What problem does it solve? Code review feedback often gets implemented blindly or met with performative agreement, leading to broken functionality, wasted effort on unused features, and missed clarification on ambiguous items. This Skill enforces a verify-first discipline when responding to review comments from PR reviewers, Codex, or automated review agents. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify against the codebase, evaluate technical soundness, then respond and implement one item at a time with individual testing. - Source-Specific Handling: Applies different trust levels for feedback from your human partner versus external reviewers, with explicit pushback guidance when suggestions are technically wrong or violate YAGNI. - Clarification-First Rule: Stops all implementation when any feedback item is unclear, preventing partial or incorrect fixes across multi-item review lists. - Use Case: A reviewer on your GitHub PR requests six changes, suggests removing legacy compatibility code, and asks for a full metrics subsystem. The Skill guides you to verify the legacy code is still needed for older build targets, grep the codebase to confirm the metrics endpoint is unused (YAGNI), ask for clarification on ambiguous items, and reply in the correct GitHub comment threads. ## Quick Start Use the receiving-code-review skill to evaluate the review comments on my current pull request before implementing any changes.
