01
It starts by itself
task done or merge. Runs in GitHub Actions or Claude Code routine.
- ↻ task done or merge
pull_request opened against main
Jesse Vincent · 260K installsPrime Radiant · Keyboardio · Request Tracker, SuperpowersRequesting Code Review skill
Runs by itself, task done or merge.
Every task reviewed before merge.
Install the Requesting Code Review skill and make it a habit: follow https://gethabit.dev/skills/obra/requesting-code-review.md
- 1Copy
- 2Paste into Claude Code, Codex or Cursor
- 3It runs by itself
260K installs303K starsMIT licenceSource on GitHub ↗
Requesting Code Review
by Jesse Vincent · 260K installs
The skill
The requesting code review skill has your agent send its diff to a fresh reviewer subagent with clean context, then fix what it finds by severity.
Only when you ask.
The habit
Every task reviewed before merge.
↻ Runs by itselftask done or merge
How the habit works.
You don't have to.
When does it start? How does it check its work? What does it remember?
One run, step by step.
Then it stops.
Stops after one review per task, with at most two fix-and-review rounds.
- 01
Get the SHAs
Find BASE_SHA and HEAD_SHA with git rev-parse or git merge-base.
- 02
Dispatch reviewer
Send a general-purpose subagent the code-reviewer.md template with description, requirements and both SHAs.
- 03
Fix Critical issues
Fix Critical issues at once and Important issues before the next task.
- 04
Note Minor issues
Write Minor issues to the loop notes for later.
- 05
Push back if wrong
If the reviewer is wrong, answer with technical reasons and code or tests.
What it may do.
Nothing more.
It writes only in its own folder and asks you before anything goes out.
- Writes only insrc/**, tests/**, loops/requesting-code-review-loop/**
- Talks tono outside service
- Sendsnothing
- Your OKNothing goes out, so it needs no OK.
Is it for you?
Use it when it fits.
Read both lists. If the left one sounds like you, the Requesting Code Review skill helps.
Use it when
- ✓ a task or feature is finished
- ✓ before a merge to main
- ✓ you are stuck on a change
Skip it when
- – there is no commit to compare
- – you review every diff by hand anyway
Requesting Code Review skill, answered.
Why a subagent and not the main agent?
The reviewer gets only the crafted context and the diff, not the session history. The main agent keeps its context for the work.
What blocks the next task?
Open Critical or Important issues. Minor issues only go on the list.
When is review mandatory?
After each task in subagent-driven work, after a major feature and before a merge to main.
How do I install the Requesting Code Review skill?
Copy the prompt at the top into your agent. It installs the skill from obra/superpowers and sets up the habit. Or run npx skills add obra/superpowers --skill requesting-code-review.
Is the Requesting Code Review skill free?
Yes. It is published under MIT. Habit is free too.
Requesting Code Review. Now as a habit.
Install the Requesting Code Review skill and make it a habit: follow https://gethabit.dev/skills/obra/requesting-code-review.md
All Jesse Vincent skills →More code skills →
Works in
- Claude Code
- Codex
- Cursor
- ChatGPT
- Claude app
Made by Jesse Vincent, published under MIT. Habit links to the original and never changes it. Is this your skill?