review-code

Pin a fixed point such as a commit SHA or branch, capture the diff with git diff <fixed-point>...HEAD, then run the Standards and Spec axes as parallel sub-agents. Each axis reports findings independently under separate headings without cross-ranking.

A two-axis review evaluates Standards (documented repo standards plus the Fowler smell baseline) and Spec (faithful implementation of the originating issue) as separate, unmerged streams. This separation prevents strong findings on one axis from masking failures on the other.

Apply adversarial heuristics targeting AI defect signatures: hallucinated APIs, missing awaits, race conditions, dropped switch branches, over-defensive null coalescing, and tautological test assertions. Verify function signatures against pinned dependency versions and trace all error paths.

Yes. If no spec is found after checking commit references, user-provided paths, and docs directories, the Spec axis still runs and reports "no spec available". The Standards axis proceeds normally with repo standards and the smell baseline.

Single-phase destructive changes like dropping or renaming a column in one deploy are rejected. Migrations must follow the zero-downtime Expand/Contract pattern: add the new column nullable, dual-write and backfill, then contract in a later release.

Skip it for informal exploratory walkthroughs that do not gate a merge, since structured contract emission is unnecessary there. It also duplicates work already enforced by automated linters and type checkers, which the review explicitly skips.