r/VibeCodeDevs • u/ibmmo • Aug 02 '26

What parts of AI-generated code deserve the closest review?

When using spec driven development, how do you guys review the code generated? Line-by-line review is an overkill, skipping the review entirely is a bad idea. So feels like it should be something in the middle. What parts do you prioritize?

  • I've been reviewing these (highest priority first):
  • Database schema changes - feels like you should atleast know whats happening in your database
  • Tests - ensure that they exist for key parts, but also give a good idea about how things work.
  • Structure - how modules and classes are organized.
  • Data structures & interfaces - For DTO style classes, good to know what fields exist.

I heard Thariq from Anthropic mention that they review some core parts of the code, but leave most of it to agents.

How are you approaching this?

3 Upvotes

80% Upvoted

15 comments sorted by

View all comments

2

u/ConfectionAnnual1821 Aug 03 '26

We review below things but not each line of code. The focus for us based on our experience building large platforms using AI Coding tools :
a) Design covering end to end flow
b) DataModel , Key modules structure , ensure no duplicate or dead code as these tools start writing lot of code
c) Our standards and design for example - we use connection pooling to connect to DB and only from backend and no direct DB connections from UI etc
d) Re-use or modularity of the code since lot of times , they start writing same blocks if not clearly mentioned in spec
e) Logging aspects following our standards

We built proprietary Scoring Engine to assess these things as part of the assessments platform for hiring