code-reviewlisted

# Code Review Review the intended change set along two independent axes: - **Standards** — conformity with repository rules and maintainable design. - **Spec** — fidelity to the original requirements, decisions, obligations, and proof contracts. Use parallel sub-agents for the axes when agent capacity exists; otherwise run them sequentially while preserving separate reports. Never let a clean Standards result hide a Spec failure or vice versa. Apply the evidence checks below directly; the review has no companion-skill dependency. ## 1. Pin the review set Resolve the fixed point supplied by the user. If none is supplied, infer the repository's normal merge base when unambiguous; otherwise ask. Record the resolved commit, branch, and commits since it. Review the merge-base-to-HEAD diff **plus** staged changes, unstaged changes, and in-scope untracked files. Inventory pre-existing dirty work so it is not silently attributed to the implementation. Fail early on a bad reference, but do not call an apparently empty committed diff empty until the working tree and untracked inventory are checked. ## 2. Find the source of truth Use tracker conventions to load the full originating ticket/spec, comments, accepted decisions, original criteria, coverage matrix, and proof receipts. Prefer explicit user references, then commit/branch references and repository conventions. If no spec exists, report that limitation; do not manufacture one. ## 3. Standards axis Read repository instr