Request Code Review
Prepare a focused review request with the change, requirements, and exact commit range.
npx skills add obra/superpowers --skill requesting-code-review What it does
A reviewer cannot reliably assess a change without knowing its intended behavior and boundaries. This skill helps the agent package implementation context and a precise diff for an independent review.
What changes after install
- Identifies the base and head revisions that define the change.
- Supplies the reviewer with requirements and a concise implementation summary.
- Separates actionable findings from issues that need clarification or evidence.
Install
Run this command with Node.js 22.20 or later and select your agent in the Skills CLI.
npx skills add obra/superpowers --skill requesting-code-review Before using Request Code Review
- Provide the change requirements and base/head Git revisions. The upstream workflow uses a reviewer subagent and the bundled code-reviewer template, so the host must support that review step.
Read the reviewed setup instructions for the selected workflow.
When to use it
- Reviewing a substantial change before integration.
- Getting a second assessment of a completed task against its requirements.
When not to use it
- Assuming an independent reviewer exists when the host agent cannot delegate.
Make the review request specific
For a change that adds pagination, provide the intended URL behavior, page size, handling of invalid page numbers, and the exact revisions containing the implementation. A reviewer can then assess both the code and the expected user experience. Sending only “review my changes” leaves important assumptions unstated.
The upstream skill uses base and head commit identifiers to define the diff and a supporting reviewer template to organize the request. It includes a description of what was built and the plan or requirements that the implementation should satisfy. This helps prevent a reviewer from judging the code against a different imagined feature.
Check available review tools
The documented workflow dispatches a reviewer subagent. That requires a host environment with an appropriate delegation capability; installing a Markdown file cannot create one. The supporting template and related files should remain available with the skill. If independent review is unavailable, describe the review as a self-review rather than implying another agent assessed it.
The reviewer also needs access to the relevant repository state and enough context to understand the interfaces being changed.
Act on evidence, not labels alone
Investigate significant findings, fix confirmed defects, and explain when a recommendation conflicts with a requirement or existing behavior. Keep test results alongside review findings: a review can catch missing requirements that a narrow test suite never exercises, but it is not a replacement for executing checks.
When comments arrive, pass the feedback and the diff it refers to into Receive Code Review so each proposed change can be checked against the code. SkillDex reviewed the instructions and template references without running a delegated review.
Related workflows
FAQ
- Does this skill include a reviewer workflow?
- It references a companion code-reviewer template in its folder. Preserve the supporting files when installing it.
- Does a review replace tests?
- No. Review can identify design and requirement problems, while tests and other checks establish specific behavior.