What problem does it solve?
This Skill helps teams approach code-review feedback with discipline, ensuring technical correctness over performative agreement and reducing the risk of misinterpretation when guidance is unclear or ambiguous.
Core Features & Use Cases
- Read feedback thoroughly: Absorb and understand the reviewer’s intent before reacting.
- Restate or seek clarification: Restate the requirement in your own words or ask clarifying questions to remove ambiguity.
- Verify against codebase reality: Check compatibility with the current implementation, tests, and constraints.
- Evaluate technical soundness: Assess whether the suggested change is appropriate for THIS codebase and project goals.
- Respond and then implement: Provide a technical acknowledgment or reasoned pushback, and implement changes one item at a time, with tests.
- Handle unclear feedback: If context is missing, stop and request clarification before proceeding.
Quick Start
Read the feedback in full, restate the requirement or ask clarifying questions, verify against the codebase, evaluate technical correctness, respond with technical acknowledgment or pushback, and implement changes one item at a time with tests.