What problem does it solve? Receiving code review feedback often triggers performative agreement or blind implementation, leading to unverified changes, broken functionality, and wasted effort on unclear or incorrect suggestions. ## Core Features & Use Cases - Structured Response Pattern: Enforces a read-understand-verify-evaluate-respond-implement sequence before touching any code. - Source-Specific Handling: Distinguishes trusted feedback from your human partner versus external reviewer suggestions that require skeptical verification against the codebase. - Pushback and YAGNI Checks: Provides criteria for pushing back on technically incorrect suggestions and grepping for actual usage before implementing "professional" features. - Use Case: A reviewer leaves six comments on your pull request, two of which are unclear. Instead of partially implementing, you clarify items 4 and 5 first, verify each suggestion against the codebase, then implement fixes one at a time with individual tests. ## Quick Start Apply the receiving-code-review skill to evaluate and respond to the review comments on my current pull request before implementing any changes.
