← All questions
How do I review AI-generated code without relying on vibes?
Write the expectations down before implementation (goal, constraints, acceptance criteria, edge cases), then review the change against that file instead of against your mood.
Without criteria, review fails in two ways: endless polishing because you cannot define good, or silent drift because you approve when tired.
A signal tells you where to look. Criteria tell you what to do next. Review against artifacts turns a debate into a check.