---
title: "Superpowers Receiving Code Review: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/obra-receiving-code-review/
description: "Checks review feedback against the code and project constraints before making and testing each requested change."
---

# Superpowers Receiving Code Review: review, setup & limitations · Undominated.ai

> Checks review feedback against the code and project constraints before making and testing each requested change.

[← Explore all skills](/skills/)

TESTING AND RELIABILITY / Jesse Vincent / Superpowers

# Superpowers Receiving Code Review

Checks review feedback against the code and project constraints before making and testing each requested change.

 See setup guidance ↓Original source ↗

SOURCE REVIEW

 Reviewed 2026-09-21
 Evidence 6 linked sources
 Publisher Jesse Vincent / Superpowers
 Licence MIT ↗
 Revision 5bf4e7801107
 Read what was—and wasn’t—checked ↓

“Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not”

 Jesse Vincent / Superpowers · upstream description ↗ Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Treats reviewer suggestions as hypotheses to verify, with explicit checks for existing behavior, platform constraints and unused functionality.
- Encourages evidence-based pushback and one change at a time with verification, instead of changing code merely to satisfy a comment.

### A good fit for

 - Working through a pull-request review
- Deciding whether a suggested refactor or fix is actually appropriate

### Weigh up before choosing

 - Its conversational tone rules are a style preference, and its pause-on-ambiguity rule may be too restrictive for independent review items.
- It does not supply a test harness or prove a reviewer is wrong; source evidence and the project’s own checks remain necessary.
- The GitHub reply example names an endpoint but omits the request method and body; use current GitHub CLI/API guidance before posting.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - skills/receiving-code-review/SKILL.md
- README.md (installation, compatibility and licence sections)
- LICENSE

### Our findings

 - The complete definition distinguishes clarification, technical disagreement and implementation, and asks the agent to state what it cannot verify.
- Replying to GitHub comments is an external write, separate from inspecting feedback or preparing code changes.

### Not established by this review

 - No review comments were acted on and no GitHub replies were sent.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

Upstream setup instructions ↗

DOCUMENTED COMMAND

 npx skills add https://github.com/obra/superpowers/tree/5bf4e78011075bcfc0dc295f0724994cd123ee71/skills/receiving-code-review Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Install the receiving-code-review directory.
- Provide the review and its target revision, then authorize the desired code changes or posted replies separately as appropriate.
- Choose the intended host and project scope in the installer. The source revision is pinned; the installer itself is not executed or version-pinned by this review.

### Before you start

 - Node.js/npm and git for the documented Skills installer
- Review comments and the relevant current code
- Project test tools; GitHub access only if you authorize posting a response

### Compatibility

Claude Code · Codex

### Review comments, code and tests

 - Read feedback and repository behavior
- Edit and test accepted fixes
- Post review replies only when requested

### Cost model

MIT-licensed instructions; agent, test infrastructure and optional GitHub service usage are separate.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - Skill definition at reviewed revision ↗ Checked 2026-09-21 https://github.com/obra/superpowers/blob/5bf4e78011075bcfc0dc295f0724994cd123ee71/skills/receiving-code-review/SKILL.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access
- Publisher installation, compatibility and licensing guidance ↗ Checked 2026-09-21 https://github.com/obra/superpowers/blob/5bf4e78011075bcfc0dc295f0724994cd123ee71/README.md Supports: install, compatibility, access, license
- Upstream licence at reviewed revision ↗ Checked 2026-09-21 https://github.com/obra/superpowers/blob/5bf4e78011075bcfc0dc295f0724994cd123ee71/LICENSE Supports: license, access.cost
- Skills installer: source formats and repeated skill selection ↗ Checked 2026-09-21 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md Supports: install
- Skills installer: full commit SHA checkout support ↗ Checked 2026-09-21 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/git.ts Supports: install
- Skills installer: tree revision and subdirectory parsing ↗ Checked 2026-09-21 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/source-parser.ts Supports: install

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Bug Receipt ↗ Creates an evidence-bearing defect or incident handoff that distinguishes verified, partial and blocked outcomes.](/skills/github-bug-receipt/)[### Superpowers Systematic Debugging ↗ Moves debugging from reproducible evidence through a single hypothesis to a verified fix, with a stop point for repeated failed attempts.](/skills/obra-systematic-debugging/)[### Superpowers Verification Before Completion ↗ Requires a fresh command result or direct check for each completion claim and distinguishes passing tests from fulfilling requirements.](/skills/obra-verification-before-completion/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)
