receiving-code-review

Guides verification and implementation of code review feedback with technical rigor.

Updated Dec 19, 2024
One-click install
npx skills add https://github.com/DNepovim/yadm --skill receiving-code-review-dnepovim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/DNepovim/yadm/tree/main/.claude/plugins/cache/claude-plugins-official/superpowers/5.0.6/skills/receiving-code-review
Command: npx skills add https://github.com/DNepovim/yadm --skill receiving-code-review-dnepovim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When receiving code review feedback, AI assistants often respond with performative agreement or blindly implement suggestions without verifying them against the actual codebase. This Skill enforces a disciplined response pattern: read, understand, verify, evaluate, then implement or push back with technical reasoning. ## Core Features & Use Cases - Structured Response Pattern: A six-step workflow (read, understand, verify, evaluate, respond, implement) that prevents premature or incorrect implementation of review feedback. - Source-Specific Handling: Different rules for feedback from a trusted human partner versus external reviewers, including verification checklists and pushback guidance. - YAGNI and Unclear-Feedback Checks: Instructions to grep the codebase for actual usage before adding features, and to stop and ask for clarification when any feedback item is unclear. - Use Case: A reviewer suggests removing legacy code or adding a metrics endpoint. Instead of agreeing, the assistant checks build targets and greps for callers, then either implements the fix, pushes back with technical reasoning, or asks for clarification. ## Quick Start Apply the receiving-code-review skill to evaluate and respond to the review comments on my current pull request.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How should I respond to code review feedback as an AI assistant?▼

Follow a six-step pattern: read the full feedback, restate the requirement, verify it against the codebase, evaluate technical soundness, respond with acknowledgment or reasoned pushback, then implement one item at a time with tests. Avoid performative phrases like "You're absolutely right!"

How do I handle unclear code review comments?▼

Stop and ask for clarification before implementing anything. Partial understanding leads to wrong implementations, especially when feedback items are related. State which items you understand and which need clarification.

When should I push back on a code review suggestion?▼

Push back when a suggestion breaks existing functionality, violates YAGNI for unused features, is technically incorrect for the stack, or conflicts with prior architectural decisions. Use technical reasoning and reference working code or tests rather than being defensive.

Should external reviewer feedback be treated differently from my team lead's feedback?▼

Yes. Feedback from a trusted human partner can be implemented after understanding, while external reviewer suggestions require verification against the codebase first. If external feedback conflicts with prior decisions, discuss with the human partner before proceeding.

How do I reply to inline review comments on GitHub pull requests?▼

Reply within the comment thread using the GitHub API endpoint for pull request comment replies, not as a top-level PR comment. This keeps the discussion attached to the specific line of code being reviewed.