Review an AI-generated diff
Read a patch as a series of behavior changes.
17 minutes
Review the boundaries first
A diff shows additions and removals. Start with the changed files and ask which behavior each change serves. Trace user input to validation, server action and saved result. Notice unrelated files, weakened checks and new dependencies.
Walk, defend, debug
Borrow three habits from the original curriculum: walk through a line, defend a design choice and describe a failure. Ask why a guard exists, what a simpler option costs and what breaks if a request repeats.