Intent, not syntax
Style, types, tests and security were already verified. The reviewer asks "is this the right change, built the right way?"
← The ADLC loop
Review: human judgment, spent where it counts.
The PRs are verified, so the engineer doesn't re-check style, types or tests. A review brief points them to the few lines that need human eyes, and they look for what machines can't judge: intent, design and blast radius.
Review brief · prepared by review-agent Preparing
#143 server-authoritative clock · coder-2 · +318 −12
Risk map
Needs human eyes—
src/game/clock.ts Waiting
Spec update · SPEC-001 v1.1 No changes
Review findings that the spec missed go back into the spec — so the next plan, build and verify all know.
Approvals & merge queue main · waiting
Human review time: 0 min for 3 PRs (1,107 changed lines)
What a human reviewer is for
Blast radius
What happens when this fails in production? Clocks that vanish on a deploy were invisible to every gate, because the spec never mentioned restarts.
Feed the spec
A finding that the spec missed becomes a new acceptance criterion and steering rule, so the whole loop learns — not just this PR.
The right reviewer
Risky areas such as database migrations pull in a code owner automatically. Low-risk PRs get a quick approval, not a ceremony.