receiving-code-review

Verify code review feedback against the codebase and implement changes with tests.

270k|24.1k|Updated Oct 9, 2025

Search Tags:#workflow #development #code review #feedback #communication #quality #technical rigor

Ready to run

npx skills add https://github.com/obra/superpowers --skill receiving-code-review-obra

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/obra/superpowers/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/obra/superpowers --skill receiving-code-review-obra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? This Skill guides the rigorous technical evaluation of code review feedback, preventing blind implementation or performative agreement. It ensures suggestions are verified against codebase reality and implemented with precision, fostering a culture of technical correctness.

Core Features & Use Cases

Technical Verification: Mandates checking feedback against the codebase, existing functionality, and architectural decisions before implementation.
Structured Response Pattern: Guides you through reading, understanding, verifying, evaluating, and then responding or implementing, ensuring a methodical approach.
Reasoned Pushback: Empowers you to push back on technically questionable feedback with clear, evidence-based reasoning, promoting critical thinking.
Use Case: When a reviewer suggests a change that seems to violate YAGNI or conflicts with a prior architectural decision, this skill guides you to verify the suggestion, and if necessary, push back with technical arguments rather than blindly implementing.

Quick Start

Example: Receiving code review feedback

WHEN receiving code review feedback:

1. READ: Complete feedback without reacting

2. UNDERSTAND: Restate requirement in own words (or ask for clarification)

3. VERIFY: Check against codebase reality (e.g., "Does this break existing functionality?")

4. EVALUATE: Is it technically sound for THIS codebase?

5. RESPOND: Technical acknowledgment or reasoned pushback

6. IMPLEMENT: One item at a time, test each

Handling Unclear Feedback:

IF any item is unclear: STOP - do not implement anything yet. ASK for clarification.

Example: "I understand items 1,2,3,6. Need clarification on 4 and 5 before proceeding."

Acknowledging Correct Feedback (actions speak louder than words):

✅ "Fixed. [Brief description of what changed]"

❌ "You're absolutely right!" (Forbidden - avoid performative agreement)

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 without just agreeing blindly?▼

Code review feedback should be verified against your codebase before implementation. Read the feedback completely, restate it in your own words, check it against existing functionality and architectural decisions, evaluate its technical soundness, then respond with either implementation or evidence-based pushback—never performative agreement.

What should I do when code review feedback is unclear or seems technically wrong?▼

Stop and ask for clarification before implementing anything. Document which items are clear and which need explanation. This prevents implementing incorrect changes and ensures the reviewer's intent is understood before you proceed with any modifications.

How do I push back on code review suggestions I disagree with?▼

Verify the suggestion against your codebase, existing functionality, and prior architectural decisions. If it conflicts with YAGNI or your design, respond with clear technical reasoning and evidence from your code. This approach fosters critical thinking and technical correctness over blind compliance.

What's the best way to handle multiple code review items at once?▼

Implement one item at a time and test each change individually. This methodical approach prevents cascading errors, makes it easier to identify which change caused problems, and ensures each modification is technically sound before moving to the next feedback item.

Why should code review feedback be checked against the codebase first?▼

Feedback that looks correct in isolation may break existing functionality, conflict with prior decisions, or violate your architecture. Verification ensures suggestions fit your specific codebase reality, preventing unnecessary refactoring or introducing bugs.

How do I structure my response when I disagree with a code review suggestion?▼

Use the READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND pattern. State what you understand, show what you verified in the codebase, explain why the suggestion is technically unsound for your context, then provide your reasoned alternative or ask clarifying questions.