What problem does it solve? Receiving code review feedback often leads to reflexive agreement, unverified implementations, or silent deferral of valid findings. This Skill enforces a disciplined workflow: verify every suggestion against the codebase before implementing, ask before assuming, and push back with technical reasoning when feedback is wrong. ## Core Features & Use Cases - Structured Response Pattern: A six-step flow (read, understand, verify, evaluate, respond, implement) that replaces performative agreement with technical evaluation. - Unclear Feedback Handling: Stops all implementation when any feedback item is ambiguous and requests clarification first, preventing partial or wrong fixes. - Out-of-Pattern Findings: Ensures reviewer findings that violate project conventions (SOLID, DRY, naming, layer boundaries) are fixed in the current PR or a follow-up, never silently deferred. - Use Case: A reviewer leaves five comments on your pull request, two of which are unclear and one that conflicts with an earlier architectural decision. The Skill guides you to clarify the unclear items first, push back on the conflicting suggestion with technical reasoning, then implement and test the valid fixes one at a time. ## Quick Start Apply the review-receive workflow to evaluate and implement the reviewer comments on my current pull request.
