cm-code-reviewlisted

# Code Review — Request + Receive + Complete ## TL;DR - **Use when** task complete, before/during PR review - **Pre-review**: lint, tests, diff scan, blast radius - **Reads**: handoff/exec.json — **Writes**: handoff/review.json - **Severity**: info | warn | error | critical - **Next**: cm-quality-gate > **Full review lifecycle in one skill:** Request → Receive → Integrate. ## Part A: Requesting Code Review ### When to Request **Mandatory:** - After each task in `cm-execution` - After completing major features - Before merge to main **Optional but valuable:** - When stuck (fresh perspective) - Before refactoring (baseline check) - After fixing complex bugs ### How to Request 1. **Get git SHAs:** ```bash BASE_SHA=$(git rev-parse HEAD~1) HEAD_SHA=$(git rev-parse HEAD) ``` 2. **Dispatch reviewer subagent** with: - What was implemented - Plan/requirements reference - Base and head SHAs - Brief description 3. **Act on feedback:** - Fix Critical issues immediately - Fix Important issues before proceeding - Note Minor issues for later - Push back if reviewer is wrong (with reasoning) --- ## Part B: Receiving Code Review ### When to Use When receiving feedback — whether from human reviewers, AI reviewers, or code review subagents. ### The Protocol ``` 1. READ feedback completely before responding 2. UNDERSTAND the technical reasoning 3. VERIFY if the feedback is technically correct 4. RESPOND with evidence, not agreement ``` ### Resp