Review
If topology=multi-module (triage announcement or coordinator spec/plan declaration), read ../references/multi-module.md. Review each module diff in its owning repository first, then review the workspace as one change set. Block missing repositories, copied or divergent shared contracts, undeclared cross-module edits, overlapping writers, incomplete local acceptance, or integration results that do not identify the tested workspace combination.
Check in order:
- Spec match (if spec exists) - diff does what the spec/plan said? List drift.
- Standards — lint/format/typecheck green? Code matches
convention, idiomatic for the stack? (see ../references/quality.md)
- Tests - new behavior covered, all green?
- Doc-coverage & Living docs —
contract covers full public surface? Env vars/config/error modes documented? README commands runnable? Living docs honor North Star (atemporal ground truth, modular specs; see ../references/quality.md)?
- Edges - null, empty, large, concurrent, malformed, unicode, timezone.
- Security - input validation, secrets, authz, injection, path traversal.
- Scope - unrelated changes? Revert. Implementation >2x necessary? Flag as FIX.
- Integration (multi-module) - dependency order, compatibility, failure propagation, and coordinator acceptance cover the exact participating modules?
For spec/plan reviews, also block unresolved implementation notes, plan assumptions absent from spec, vague acceptance, or premature [parallel].
Report:
BLOCK: <must fix>
FIX: <should fix>
NIT: <optional>
BLOCKs resolved before merge. FIX resolved or explicitly deferred with reason.
1---2name: review3description: Use before merge, after subagents, or for spec/plan review.4---56# Review78If `topology=multi-module` (triage announcement or coordinator spec/plan declaration), read `../references/multi-module.md`. Review each module diff in its owning repository first, then review the workspace as one change set. Block missing repositories, copied or divergent shared contracts, undeclared cross-module edits, overlapping writers, incomplete local acceptance, or integration results that do not identify the tested workspace combination.910Check in order:111. **Spec match** (if spec exists) - diff does what the spec/plan said? List drift.122. **Standards** — lint/format/typecheck green? Code matches `convention`, idiomatic for the stack? (see `../references/quality.md`)133. **Tests** - new behavior covered, all green?144. **Doc-coverage & Living docs** — `contract` covers full public surface? Env vars/config/error modes documented? README commands runnable? Living docs honor North Star (atemporal ground truth, modular specs; see `../references/quality.md`)?155. **Edges** - null, empty, large, concurrent, malformed, unicode, timezone.166. **Security** - input validation, secrets, authz, injection, path traversal.177. **Scope** - unrelated changes? Revert. Implementation >2x necessary? Flag as FIX.188. **Integration** (multi-module) - dependency order, compatibility, failure propagation, and coordinator acceptance cover the exact participating modules?1920For spec/plan reviews, also block unresolved implementation notes, plan assumptions absent from spec, vague acceptance, or premature `[parallel]`.2122Report:23```24BLOCK: <must fix>25FIX: <should fix>26NIT: <optional>27```28BLOCKs resolved before merge. FIX resolved or explicitly deferred with reason.
hashgraph-online