receiving-code-review

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

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/Pega88/agy-superpowers --skill receiving-code-review-pega88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Pega88/agy-superpowers/tree/main/.agents/plugins/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/Pega88/agy-superpowers --skill receiving-code-review-pega88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often leads to two failure modes: performative agreement without verification, or blind implementation of suggestions that may break the codebase. This Skill enforces a disciplined response pattern so feedback is evaluated against codebase reality before any changes are made. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, then implement feedback one item at a time with individual testing. - Source-Specific Handling: Differentiates between trusted feedback from your human partner and external reviewer suggestions that require skeptical verification. - Pushback and YAGNI Checks: Provides criteria for pushing back with technical reasoning and checking whether suggested features are actually used before implementing them. - Use Case: A reviewer leaves six comments on your pull request, two of which are unclear and one suggesting an unused feature. The Skill directs you to clarify the unclear items first, verify the feature against actual codebase usage, and implement confirmed fixes one at a time. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my current pull request before implementing any changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I respond to code review feedback professionally?

Restate the technical requirement, verify it against the codebase, then implement or push back with reasoning. Avoid performative phrases like "great point" or "you're absolutely right" and let the code changes demonstrate the response.

How to handle unclear code review comments?

Stop and ask for clarification before implementing anything when feedback items are unclear. Partial understanding leads to wrong implementation because review items are often related to each other.

When should I push back on code review suggestions?

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 tests or code.

Should I implement all external reviewer feedback immediately?

No. External reviewer feedback should be verified first: check technical correctness for the codebase, whether it breaks existing functionality, and whether the reviewer has full context. State limitations if you cannot verify a suggestion.

How do I reply to inline GitHub review comments?

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