Skip to content
Coding

Receive Code Review

Evaluate review comments against the actual code before making changes.

Install with Skills CLI
npx skills add obra/superpowers --skill receiving-code-review

What it does

Blindly accepting review feedback can replace a working decision with an inappropriate change. This skill helps the agent understand each comment, verify its technical basis, and respond with a concrete fix or explanation.

What changes after install

  • Checks whether feedback applies to the current code, versions, and requirements.
  • Clarifies consequential ambiguity before implementing a recommendation.
  • Applies confirmed changes in a controlled order with relevant checks.

Install

Run this command with Node.js 22.20 or later and select your agent in the Skills CLI.

Install with Skills CLI
npx skills add obra/superpowers --skill receiving-code-review

Before using Receive Code Review

  • Provide the actual review comments and the current code. The agent needs enough project context and runnable checks to evaluate each suggestion before applying it.

Read the reviewed setup instructions for the selected workflow.

When to use it

  • Working through external review comments on a pull request.
  • Resolving feedback that may conflict with compatibility or product requirements.

When not to use it

  • Rejecting feedback reflexively or using the workflow to avoid correcting a demonstrated defect.

Start from the behavior the comment concerns

Suppose a reviewer asks you to remove a compatibility branch. Before deleting it, identify the supported versions, the original reason for the branch, and any tests that depend on it. The recommendation may be correct, but the codebase provides the evidence needed to decide.

The skill separates reading a comment from agreeing with it. It asks the agent to understand the request, verify it against the repository, and determine whether the proposed change fits the actual constraints. This is particularly useful when automated feedback is technically plausible but ignores a platform or legacy requirement.

Make corrections reviewable

For confirmed issues, change one coherent behavior at a time and run the relevant checks. A short response that identifies the fix and where it was made is more useful than a lengthy expression of agreement. If a recommendation cannot be verified with the available environment, preserve that uncertainty instead of treating it as resolved.

For related comments, clarify any ambiguity that could change the implementation before making a partial fix. Do not use uncertainty about a minor preference to delay an independently confirmed defect.

Keep disagreement concrete

A useful disagreement cites the affected behavior, current requirements, or a reproducible result. It should also leave room for the reviewer to supply missing context. The workflow does not authorize sending comments to other people by itself; communication still depends on the user’s instructions and available tools.

Choose Request Code Review when preparing the assessment and this skill when responding to its results. SkillDex reviewed the source workflow and did not apply it to a live pull request.

FAQ

Should every reviewer suggestion be implemented?
No. Verify the issue in the project's context; explain with evidence when a suggestion would break an existing requirement.
What if a comment is unclear?
Clarify the behavior or scope that matters before changing code, especially when several comments depend on each other.