← Explore all 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.

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

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.

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

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

  1. Install the receiving-code-review directory.
  2. Provide the review and its target revision, then authorize the desired code changes or posted replies separately as appropriate.
  3. 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

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. https://github.com/obra/superpowers/blob/5bf4e78011075bcfc0dc295f0724994cd123ee71/skills/receiving-code-review/SKILL.md

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access

  2. https://github.com/obra/superpowers/blob/5bf4e78011075bcfc0dc295f0724994cd123ee71/README.md

    Supports: install, compatibility, access, license

  3. https://github.com/obra/superpowers/blob/5bf4e78011075bcfc0dc295f0724994cd123ee71/LICENSE

    Supports: license, access.cost

  4. https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md

    Supports: install

  5. https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/git.ts

    Supports: install

  6. https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/source-parser.ts

    Supports: install