What problem does it solve?
Code review requires technical evaluation, not emotional performance. This Skill helps engineers verify feedback before implementing changes, restate requirements clearly, and ask clarifying questions to avoid misinterpretation.
Core Features & Use Cases
- Structured response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT steps to address feedback safely.
- Unclear feedback handling: If any item is unclear, STOP and ask for clarification before proceeding.
- Source-specific handling: Distinguish between trusted human partners and external reviewers, and push back with technical reasoning when needed.
- YAGNI-driven checks: Avoid adding features or changes unless they are truly required by the codebase.
- Implementation order: Prioritize blocking issues, then simple fixes, then complex changes; test each step.
- Push-back discipline: Use technical justification and ask targeted questions when a suggestion seems risky or incorrect.
- Graceful correction: Correct course with factual updates rather than apologies when feedback is challenged.
Quick Start
Restate the technical requirement in your own words, verify it against the codebase, and implement changes one item at a time.
