What problem does it solve? Receiving code review feedback often triggers performative agreement or blind implementation, leading to broken code, wasted effort on unclear items, and unverified suggestions from external reviewers. This Skill enforces a verify-before-implement discipline so feedback is evaluated against the actual codebase 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 trusted feedback from your human partner versus external reviewer suggestions that require skepticism and codebase 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 leaves six comments on your pull request, two of which are unclear. Instead of guessing, you clarify items 4 and 5 first, verify the rest against the codebase, then implement and test each fix individually. ## 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.
