receiving-code-review

Process and verify code review feedback to produce prioritized GitHub replies.

12|2|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/aman-2709/superpowers-ecc --skill receiving-code-review-aman-2709
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/aman-2709/superpowers-ecc/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/aman-2709/superpowers-ecc --skill receiving-code-review-aman-2709

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and agents process incoming code review feedback in a verification-first way to avoid performative agreement, prevent incorrect changes, and ensure technical correctness before implementation.

Core Features & Use Cases

  • Structured response pattern: Follow a clear sequence — read, restate, verify, evaluate, respond, then implement each item one at a time.
  • Reviewer-aware guardrails: Different handling for human partners versus external reviewers, checks for compatibility, YAGNI, and regression risk.
  • Practical communication templates: Concrete phrasing for clarifying ambiguous items, pushing back with technical reasoning, acknowledging correct feedback succinctly, and correcting mistaken pushback.
  • Use case: When a developer receives PR comments or inline suggestions, use this Skill to verify applicability, prioritize fixes, request clarifications, and produce concise GitHub replies or implementation steps.

Quick Start

When you receive review comments, restate understood items, ask for clarification on unclear ones, verify against the codebase, and propose an ordered implementation plan.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I process code review feedback on a pull request without making incorrect changes?

Process code review feedback by reading, restating intent, verifying against the codebase, evaluating for compatibility, and prioritizing fixes by severity before implementing changes. This prevents performative agreement and ensures technical correctness.

What is the best way to respond to ambiguous code review comments on GitHub?

The best way to respond to ambiguous code review comments is to restate the understood intent and request clarifying information using practical communication templates before writing any code, ensuring the reviewer's actual concern is addressed.

How do I push back on code review suggestions that violate YAGNI or introduce regression risk?

Push back on erroneous code review suggestions by verifying the comment against your codebase constraints and replying with concise technical reasoning. Use the structured response pattern to correct mistaken pushback with evidence.

Can I use a structured workflow to prioritize technical feedback from teammates during refactoring?

Yes, you can use a verification-first workflow to prioritize technical feedback during refactoring. Evaluate each suggestion against YAGNI principles and regression risk, then propose an ordered implementation plan to address fixes by severity.

When do I need to verify external reviewer suggestions against my local codebase?

Verify external reviewer suggestions against your local codebase whenever you receive inline review notes or pull request comments to ensure compatibility. This prevents incorrect changes and ensures technical correctness before implementation.

Does handling pull request comments require different guardrails for human partners versus external reviewers?

Yes, handling pull request comments requires reviewer-aware guardrails. Differentiate between human partners and external reviewers to appropriately check for compatibility, YAGNI violations, and regression risk before producing GitHub replies.