code-reviewlisted

# code-review ## Overview | Field | Contract | | --- | --- | | Purpose | Apply one review discipline for diffs, feedback, and completion claims. | | Primary input | PR, commit, pending diff, codebase scope, reviewer feedback, or completion claim. | | Primary output | Findings-first verdict, feedback response, verification gate result, or fix-review cycle. | | Boundary | Do not claim done/fixed/passing without fresh verification evidence. | | Next handoff | Fix highest-severity findings, re-run verification, then ship when ready. | Use one review discipline everywhere: receive feedback rigorously, request adversarial review, and make completion claims only with fresh evidence. There is no separate review command or wrapper. Invoke this skill directly (`/code-review`) for standalone reviews, feedback reception, and completion gates. cook, fix, and ship dispatch the `code-reviewer` agent directly with their own scoped context (diff, root-cause claim, plan, and current verification evidence) — they share this skill's verdict contract but do not re-run the standalone protocol below on top of their own review steps. ## Resources | Practice | Load When | File | | --- | --- | --- | | Receiving feedback | Reviewer comments are unclear, risky, or conflict with local context | `references/code-review-reception.md` | | Requesting review | Cook/fix finished a phase, before merge, or standalone review is requested | `references/requesting-code-review.md` | | Verification gates | Befo