What problem does it solve? Code review feedback often triggers performative agreement or blind implementation, leading to broken code, unverified changes, and missed clarification opportunities. This Skill enforces a disciplined response pattern: verify feedback against the codebase before implementing, ask when unclear, and push back with technical reasoning when suggestions are wrong. ## Core Features & Use Cases - Six-Step Response Pattern: Read, understand, verify, evaluate, respond, and implement feedback one item at a time with individual testing. - Sub-Scenario Routing: Dedicated references for unclear feedback, source-specific handling (human partner vs. external reviewer), pushback and correction, implementation ordering, and common mistakes. - Forbidden Response Guardrails: Blocks performative phrases like "You're absolutely right!" and gratitude expressions, replacing them with technical acknowledgment or direct action. - Use Case: A reviewer suggests removing legacy code. Instead of agreeing immediately, you check build targets, discover backward-compatibility constraints, and respond with a reasoned technical question before changing anything. ## Quick Start Use the receiving-code-review skill to evaluate and respond to this pull request feedback before implementing any changes.
