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 protocols for trusted human partner feedback versus external reviewer suggestions, including YAGNI checks for unused features. - Pushback Guidance: Rules for when and how to push back with technical reasoning, plus how to gracefully correct yourself when your pushback was wrong. - Use Case: A reviewer suggests removing legacy code. Instead of agreeing immediately, you verify the build target and discover the legacy path is needed for backward compatibility, then respond with the technical finding. ## Quick Start Apply the receiving-code-review skill to evaluate and respond to the review comments on my current pull request.
