obra/superpowers@receiving-code-review

Restate code review feedback, verify against the codebase, and prioritize fixes by severity.

9|2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill obra-superpowers-receiving-code-review-allbeingsfuture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obra/superpowers@receiving-code-review
Source: https://github.com/AllBeingsFuture/AllBeingsFuture/tree/main/electron/embedded-assets/skills/superpowers-receiving-review
Command: npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill obra-superpowers-receiving-code-review-allbeingsfuture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers process incoming code review feedback safely and effectively by enforcing verification before implementation, avoiding performative agreement, and preventing incorrect or premature changes.

Core Features & Use Cases

  • Verification-first workflow: read feedback fully, restate the requirement, verify against the codebase, evaluate technical correctness, then respond and implement.
  • Risk reduction and prioritization: identify blocking/security issues first, perform simple fixes next, and test each change to avoid regressions.
  • Communication patterns: provide guidance for asking clarifying questions, pushing back with technical reasoning, acknowledging correct feedback concisely, and replying in GitHub thread contexts. Use cases include responding to pull request comments, triaging multi-item review feedback, and handling external reviewer suggestions while preserving project constraints.

Quick Start

Analyze the following code review comments, restate each requested change in your own words, flag items that require verification against the codebase, and propose a prioritized implementation plan.

Frequently Asked Questions about obra/superpowers@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 blindly implementing changes?

To respond to code review feedback safely, restate each request, verify it against the codebase reality, evaluate technical correctness, and prioritize fixes by severity before implementation. This prevents performative agreement and incorrect changes.

What is the best way to triage multi-item pull request comments in GitHub?

Triage multi-item pull request comments by identifying blocking or security issues first, performing simple fixes next, and testing each change to avoid regressions. Restate requirements to ensure accurate PR triage and structured review reception.

How do I push back on a code review suggestion with technical reasoning?

Push back on code review suggestions by verifying the feedback against your codebase, evaluating its technical correctness, and providing reasoned technical pushback instead of performative agreement. Acknowledge correct feedback concisely.

Can I use a structured workflow for handling external reviewer suggestions in GitHub?

Yes, you can apply a verification-first developer workflow to external reviewer suggestions in GitHub. This involves reading feedback fully, verifying against project constraints, and responding within GitHub thread contexts to ensure technical rigor.

Why do I need to verify codebase reality before implementing pull request fixes?

Verifying codebase reality before implementing pull request fixes prevents incorrect or premature changes. This verification-first workflow ensures requested changes are evaluated for technical correctness and prioritized by severity to reduce risk.