Requesting Code Review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Install
/plugin marketplace add obra/superpowersThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add obra/superpowers --skill requesting-code-reviewgit clone --depth 1 https://github.com/obra/superpowers.git /tmp/superpowers
mkdir -p ~/.claude/skills
cp -r /tmp/superpowers/skills/requesting-code-review ~/.claude/skills/requesting-code-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Requesting Code Review
Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history.
**Core principle:** Review early, review often.
## When to Request Review
**Mandatory:**
- After each task in subagent-driven development
- After completing major feature
- Before merge to main
**Optional but valuable:**
- When stuck (fresh perspective)
- Before refactoring (baseline check)
- After fixing complex bug
## How to Request
**1. Get git SHAs:**
```bash
BASE_SHA=$(git rev-parse HEAD~1) # or: git merge-base origin/main HEAD
HEAD_SHA=$(git rev-parse HEAD)
```
**2. Dispatch code reviewer subagent:**
Dispatch a `general-purpose` subagent, filling the template at [code-reviewer.md](code-reviewer.md)
**Placeholders:**
- `{DESCRIPTION}` - Brief summary of what you built
- `{PLAN_OR_REQUIREMENTS}` - What it should do
- `{BASE_SHA}` - Starting commit
- `{HEAD_SHA}` - Ending commit
**3. Act on feedback:**
- Fix Critical issues immediately
- Fix Important issues before proceeding
- Note Minor issues for later
- Push back if reviewer is wrong (with reasoning)
## ExampleDetails
- Skill name
requesting-code-review- Repository
- obra/superpowers
- Path
skills/requesting-code-review/SKILL.md- License
- MIT
- Repo updated
- 29 October 2026
FAQ
What does the Requesting Code Review skill do?
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
How do I install the Requesting Code Review skill?
Claude Code plugin: /plugin marketplace add obra/superpowers. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Requesting Code Review popular?
It lives in obra/superpowers, which has 309,696 GitHub stars and 27,549 forks, and is included in 6 curated skill lists.
Related skills
Brainstorming
310kobra/superpowers
Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.
Diagnosing Superpowers
310kobra/superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Dispatching Parallel Agents
310kobra/superpowers
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Rea Changelog Update
414kmorluto/rea
Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
Receiving Code Review
310kobra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Code Review
308kmattpocock/skills
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.