Requirements
Bring these inputs.
- The change diff and base revision
- The approved plan or acceptance criteria
- Relevant test commands
Output contract
Know what done looks like.
A review with verified findings, file references, and explicit residual risk
Execution
Run the playbook.
- 01
Lock the review boundary
List the requested behavior, changed files, and verification commands before judging the code.
CopiedSummarize the change contract and identify any requirement that cannot be verified from the provided context. - 02
Inspect for behavioral risk
Trace changed inputs, state transitions, errors, and downstream consumers.
CopiedFind correctness, security, data-loss, and regression risks. Ignore style unless it obscures a defect. - 03
Reproduce each finding
Run or write the smallest check that proves each suspected issue before reporting it.
CopiedFor every candidate finding, provide evidence, impact, exact location, and a reproducible verification step. - 04
Deliver the review
Rank only confirmed issues, then state missing tests and residual risk separately.
CopiedOutput findings first by severity, followed by open questions and a two-sentence summary.
Field note
How to use this route.
This workflow treats review as verification, not opinion generation. A finding is not ready until the reviewer can show how it fails or why the behavior violates the contract.