receiving-code-review

Verifies code review suggestions before implementing them in your codebase, one at a time with testing.

3|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/pedropaulovc/agent-plugins --skill receiving-code-review-pedropaulovc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/pedropaulovc/agent-plugins/tree/main/plugins/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/pedropaulovc/agent-plugins --skill receiving-code-review-pedropaulovc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents teams from accepting unclear, technically questionable, or performative code review feedback and accidentally implementing changes without verification.

Core Features & Use Cases

  • Verification-first reception: Reads feedback completely, restates requirements, and checks against codebase reality before acting.
  • Technical acknowledgment and reasoned pushback: Responds with evidence-based critique when suggestions are wrong, conflicting, or not verifiable.
  • Unclear-feedback gating: Stops implementation and asks targeted clarifying questions when any item is ambiguous or incomplete.
  • Implementation discipline: Handles multi-item feedback by clarifying first, applying changes one item at a time, testing each, and avoiding regressions.

Quick Start

Use receiving-code-review whenever you receive pull request or inline review comments and need to verify each suggested change against the existing codebase before implementing.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I handle pull request feedback without introducing regressions?

Handling pull request feedback without regressions requires a verification-first workflow that reads suggestions completely, restates requirements, and checks against codebase reality before implementing any changes. This prevents unverified or performative adoption of code review suggestions.

What is the best way to respond to technically questionable code review suggestions?

Responding to technically questionable code review suggestions involves providing evidence-based critique and reasoned pushback. You must evaluate each suggestion against the specific codebase to identify wrong, conflicting, or unverifiable feedback before agreeing to implement it.

How do I ask for clarification on ambiguous code review comments?

Asking for clarification on ambiguous code review comments requires gating implementation until all items are clear. You should stop implementation and ask targeted clarifying questions whenever any feedback item is incomplete or ambiguous.

How do I implement multiple code review changes without causing technical debt?

Implementing multiple code review changes without technical debt requires handling feedback one item at a time with testing. Clarify all unclear points first, then apply changes sequentially to avoid regressions and performative agreement.

When should I push back on code review feedback instead of accepting it?

You should push back on code review feedback when suggestions are technically wrong, conflict with prior decisions, or cannot be verified against the current codebase. Enforcing a response workflow ensures evidence-based critique rather than performative gratitude.

Does YAGNI apply when receiving code review suggestions?

YAGNI applies to receiving code review suggestions by enforcing engineering rigor when evaluating feedback. You must verify that each suggested change is necessary and does not introduce unverified or performative adoption that leads to technical debt.