What problem does it solve? Receiving code review feedback often triggers performative agreement or blind implementation, leading to wrong changes, broken functionality, or unverified assumptions. This Skill enforces a disciplined response pattern: read, understand, verify against the codebase, then implement or push back with technical reasoning. ## Core Features & Use Cases - Structured Response Pattern: A six-step workflow (read, understand, verify, evaluate, respond, implement) that prevents premature agreement and batch implementation without testing. - Source-Specific Handling: Different rules for feedback from a trusted human partner versus external reviewers, including YAGNI checks for suggested features and pushback guidance when suggestions conflict with prior architectural decisions. - Use Case: A reviewer on a GitHub pull request suggests removing legacy code and adding a metrics endpoint. Instead of agreeing, you grep the codebase, find the endpoint is uncalled and the legacy code is needed for backward compatibility, then reply in the review thread with technical reasoning. ## Quick Start Use the ct-receiving-code-review skill to evaluate the review comments on my pull request before I implement anything.
