PlugWiki

requesting-code-review Skill for Claude: What It Does and How to Install It

Makes Claude hand finished work to a fresh reviewer subagent, then fix the serious findings before it moves on.

Installs
269.1K
on skills.sh
Stars
310.6K
on GitHub
Files
1
besides SKILL.md
Updated
Oct 2026
last repo commit

requesting-code-review makes Claude stop after a task or feature and send the change to a separate reviewer subagent. Claude picks base and head commits with git, fills in a review template with what you built and what it should do, and gives the reviewer only that, never your session history.

It applies after each task in subagent-driven development, after a major feature, and before merging to main. Claude fixes Critical issues at once, fixes Important ones before continuing, notes Minor ones for later, and pushes back with reasoning if the reviewer is wrong. It bundles one template file, code-reviewer.md, and no scripts.

Good for

  • Developers who let Claude build features across several tasks
  • Solo developers who want a second look before merging
  • Teams using the superpowers plugin workflow

Install requesting-code-review

Claude Code

  1. 1

    Copy this prompt.

    Install the requesting-code-review skill in Claude Code. Run this command:
    
    npx skills add https://github.com/obra/superpowers --skill requesting-code-review
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Sections in SKILL.md

  1. When to Request Review
  2. How to Request
  3. Example
  4. Common Rationalizations
  5. Red Flags

Key facts

Author
obra
Installs on skills.sh
269,131 (Nov 2026)
GitHub stars
310,635 (Nov 2026)
License
MIT
Last repo commit
Oct 29, 2026
Files in the skill folder
2 including SKILL.md

What it includes

  • Finds the base and head commits of the work to review

    Runs code · Get git SHAs

  • Fills the code-reviewer.md template and sends it to a general-purpose subagent

    Read · Dispatch the reviewer

  • Fixes Critical and Important issues, notes Minor ones, pushes back if wrong

    Write · Act on feedback

  • Required after each task, after a major feature and before merge

    When to request

From the official docs

Permissions

Low risk

It runs git commands to find commit SHAs and dispatches a reviewer subagent. Claude then edits code to fix what the reviewer finds.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It runs git and dispatches a subagent

    The SKILL.md example runs git rev-parse for the base and head SHAs. A clean review is not a test run, so run your tests before you merge (our advice, not SKILL.md's).

Questions

How do I install requesting-code-review?

Use the install box above. It is one skill in the obra/superpowers repo, and its review template, code-reviewer.md, sits in its own folder.

When does Claude use it?

SKILL.md makes review mandatory after each task in subagent-driven development, after a major feature and before merging to main. It is optional when Claude is stuck, before a refactor and after a complex bug fix.

Does the reviewer see my whole conversation?

No. The skill says the reviewer gets precisely crafted context, never your session history. Claude passes a short description, the requirements, and the two commit SHAs.

Is it safe?

It runs git commands (git rev-parse, or git merge-base in the SKILL.md example) to find commit SHAs, then dispatches a general-purpose subagent with a description, the requirements and the two SHAs. Claude then fixes the issues the reviewer reports, so review those changes in git as usual.

How is it different from verification-before-completion?

This skill sends the change to a separate reviewer subagent. verification-before-completion makes Claude run the command that proves a claim (tests, build, linter) and read its output before saying work is done. They check different things and can be used together.

Information

updated Nov 2, 2026

Folder
skills/requesting-code-review

obra/superpowersskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 2
  1. requesting-code-review SKILL.md · github.com
  2. verification-before-completion SKILL.md · github.com

Updated Nov 2, 2026.