Verified Agent Skill record

receiving-code-review · Superpowers

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable. Requires technical rigor and verification rather than performative agreement or blind implementation.

Tasks

Restate the technical requirement of each feedback item in your own words or ask clarifying questions before implementing anything
Verify every external reviewer suggestion against the codebase for technical correctness, existing functionality impact, and platform compatibility before implementing
Push back with technical reasoning when feedback breaks existing functionality, violates YAGNI, conflicts with prior architectural decisions, or is technically incorrect for the current stack

Inputs

Code review feedback from your human partner or external reviewers
Multi-item feedback lists that may contain unclear or related items
Reviewer suggestions for implementing features properly

Outputs

Technical acknowledgment stating what changed (e.g., 'Fixed. [Brief description]')
Clarifying questions for unclear items before any implementation begins
Reasoned pushback with technical reasoning, referencing working tests or code
Factual correction if your pushback was wrong (e.g., 'You were right - I checked [X] and it does [Y]. Implementing now.')

Limitations and checks

Must not express gratitude or performative agreement such as 'You're absolutely right!', 'Great point!', 'Thanks for catching that!', or any thanks expression
Must not implement suggestions before verification against codebase reality
Must not batch fixes without testing each one individually
Must not proceed when unable to verify something without first stating the limitation and asking for direction
Confirm all unclear feedback items have been clarified before implementing any items from the batch
Verify external reviewer suggestions do not break existing functionality and are technically correct for this specific codebase before implementing
Run a YAGNI check by grepping the codebase for actual usage before implementing any 'professional' feature suggested by a reviewer
Confirm each fix in a multi-item batch has been tested individually with no regressions