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 technically before any code changes are made. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify against the codebase, evaluate, respond, then implement one item at a time with individual testing. - Source-Specific Handling: Different rules for trusted human partner feedback versus external reviewer suggestions, including pushback guidance and YAGNI checks for unused features. - 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 the endpoint is never called, then push back with technical reasoning. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my current pull request before implementing anything.
