full-review
Full Review
Find the risks a focused implementation pass cannot see, and return a verdict the author can act on. The review is done when its scope, evidence, findings, verification limits, and verdict are explicit.
Plan
The plan is a scope contract: it names what will be reviewed, by which seats, with which checks. Coverage outside it is never claimed, and a seat or check that quietly drops out is a broken contract.
| Scope | Use when | Shape | Route |
|---|---|---|---|
focused |
One bounded change with local risk | One seat plus relevant checks | review |
seam |
Integrated tasks, shared contracts, cross-boundary behavior | Logic-and-state coverage plus root-cause precision | deep-review |
deep |
Explicit request, security boundary, migration, public contract, high residual risk | Seam shape plus the specialists the diff triggers, and a skeptic for unproven blockers | deep-review |
A requirements document uses review. Take the scope the caller passes; otherwise choose the narrowest one the evidence supports. For code, python3 scripts/review_scope.py --base <ref> reports diff size and risk signals (migrations, API, frontend) to confirm or narrow it.
Resolve each route with python3 shared/scripts/model_routing.py resolve <route> --provider <host>; the reviewer resolves to the other provider than the host. Show the scope, each seat with its lens, model, and effort, and the planned checks, and ask: "Approve this plan, or specify changes." A plan the calling workflow already approved counts.