What problem does it solve? Receiving code review feedback often leads to two failure modes: performative agreement without verification, or blind implementation of suggestions that may break the codebase. This Skill enforces a disciplined response pattern so feedback is evaluated against codebase reality before any changes are made. ## 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: Differentiates between trusted feedback from your human partner and external reviewer suggestions that require skeptical verification. - Pushback and YAGNI Checks: Provides criteria for pushing back on technically incorrect suggestions and checking whether proposed features are actually used before implementing them. - Use Case: A reviewer on your GitHub pull request suggests removing legacy code and adding a metrics endpoint. Instead of agreeing immediately, you verify the legacy code is still needed for backward compatibility and grep the codebase to confirm nothing calls the metrics endpoint, then 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 current pull request.
