What problem does it solve? Receiving code review feedback often leads to performative agreement, blind implementation of questionable suggestions, or partial fixes when items are unclear. This Skill enforces a disciplined response pattern: verify feedback against the codebase before implementing, ask for clarification on unclear items, and push back with technical reasoning when suggestions are wrong. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, then implement feedback one item at a time with individual testing. - Source-Specific Handling: Different rules for trusted human partner feedback versus external reviewer suggestions, including YAGNI checks for unused features. - Pushback and Correction Guidance: Concrete scripts for pushing back on incorrect feedback and gracefully correcting yourself when your pushback was wrong. - Use Case: A reviewer on your GitHub PR suggests removing legacy code and adding a metrics endpoint. Instead of agreeing, you verify the legacy code is needed for backward compatibility, grep the codebase to confirm the endpoint is unused, and reply in the review thread 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 anything.
