What problem does it solve? Code review feedback often triggers performative agreement or blind implementation, leading to broken code, unverified changes, and wasted effort on unnecessary features. This Skill enforces a disciplined response pattern: verify before implementing, ask before assuming, and push back with technical reasoning when suggestions are wrong. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, and implement feedback one item at a time with individual testing. - Source-Specific Handling: Differentiates between trusted feedback from your human partner and external reviewer suggestions that require skeptical verification against the codebase. - YAGNI Enforcement: Checks whether suggested features are actually used in the codebase before implementing them. - Use Case: A reviewer on your GitHub PR suggests removing legacy code and adding a metrics endpoint. Instead of agreeing immediately, you verify the legacy code is needed for backward compatibility and grep the codebase to find the metrics endpoint is never called, then push back with technical reasoning. ## Quick Start Use the receiving-code-review skill to help me evaluate and respond to the review comments on my pull request before implementing any changes.
