What problem does it solve?
This Skill solves the common problem of unprofessional, unverified responses to code review feedback that lead to unnecessary code changes, introduced bugs, or wasted development effort, replacing performative agreement and blind implementation with a structured, technically rigorous process.
Core Features & Use Cases
- Structured 6-Step Response Workflow: A repeatable process (read, understand, verify, evaluate, respond, implement) to ensure all feedback is fully assessed before taking action.
- Scenario-Specific Guidance: Clear rules for handling unclear feedback, feedback from external reviewers versus human partners, YAGNI checks for unnecessary feature requests, and reasoned pushback for technically incorrect suggestions.
- Best Practice Templates: Concrete examples of correct responses for acknowledging valid feedback, correcting mistaken pushback, and replying to GitHub inline review comments.
- Use Case: When a reviewer requests removal of legacy code, you first verify if it is required for backward compatibility instead of immediately agreeing, avoiding breakage for users on older supported versions.
Quick Start
Use the receiving-code-review skill to respond to the code review feedback on your latest pull request, verifying each suggestion against the codebase and project requirements before implementing any changes.