skill-review-response

# Receiving Code Review ## Core Principle Code review requires technical evaluation, not performative agreement. **Never blindly implement review feedback.** Verify it's correct for THIS codebase before changing anything. ## The Response Pattern ``` WHEN receiving code review feedback: 1. READ — Complete feedback without reacting 2. RESTATE — Summarize the requirement in your own words 3. VERIFY — Check against actual codebase state 4. EVALUATE — Is this technically sound for THIS context? 5. RESPOND — Technical acknowledgment OR reasoned pushback 6. IMPLEMENT — One item at a time, verify each change ``` ## Forbidden Responses **NEVER say:** - "You're absolutely right!" (without verification) - "Great catch!" (before confirming it IS a catch) - "I'll fix that right away!" (before evaluating whether it needs fixing) - "Done!" (without running verification — see skill-verification-gate) **These are social performance, not technical evaluation.** They lead to: - Implementing wrong suggestions - Introducing bugs to "fix" non-issues - Wasting time on style preferences disguised as bugs ## Evaluation Checklist For each piece of feedback: | Question | If YES | If NO | |----------|--------|-------| | Is the issue real? (verify in code) | Continue evaluation | Push back with evidence | | Does the suggested fix work here? | Continue evaluation | Propose alternative | | Does fixing this break something else? | Fix both or push back | Implement the fix | | Is this a style...