Skill Tracer
Skills › Superpowers › requesting-code-review

requesting-code-review

skill · 95 lines · MIT · skills/requesting-code-review/SKILL.md

The facts

Its description

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

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent reaches for this skill when a piece of work has just been finished — a task, a major feature, or a branch about to merge — and the work needs to be checked against its requirements before the agent moves on.

Things a person might say (the model's guesses)

  • “I just finished the login feature — can you review it before I merge?”
  • “Task 2 is done, let's get it reviewed before starting the next one.”
  • “I'm about to merge this branch to main; can you check it meets the requirements?”

A model's summary of when it is used.

A model's reading

Starts other agents

7 lines mention starting other agents (first 5 linked)

Lines in the file that mention starting another agent. Found by matching words, so treat them as pointers.

Found by matching wordsline 8 line 15 line 32 line 34 line 58

Files it mentions

code-reviewer.md

Files the text names, such as ones to read or write. Found by matching words, so treat them as pointers.

Found by matching wordsline 34 line 95

What leads to it

Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.

A model's reading

Licence

MIT, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text
Other files in this skill (1) Close

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: requesting-code-review
3description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements
4---
5
6# Requesting Code Review
7
8Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history.
9
10**Core principle:** Review early, review often.

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.

Raw lines 1 to 11
Starts an agent Dispatch :8
Starts an agent subagent :8
12## When to Request Review
14**Mandatory:**
16- After completing major feature
17- Before merge to main
19**Optional but valuable:**
20- When stuck (fresh perspective)
21- Before refactoring (baseline check)
22- After fixing complex bug

When to Request Review

Mandatory:

Optional but valuable:

  • When stuck (fresh perspective)
  • Before refactoring (baseline check)
  • After fixing complex bug
Raw lines 12 to 23
Names a skill subagent-driven-development :15
24## How to Request
26**1. Get git SHAs:**
27```bash
28BASE_SHA=$(git rev-parse HEAD~1) # or: git merge-base origin/main HEAD
29HEAD_SHA=$(git rev-parse HEAD)
30```
32**2. Dispatch code reviewer subagent:**
34Dispatch a `general-purpose` subagent, filling the template at [code-reviewer.md](code-reviewer.md)
36**Placeholders:**
37- `{DESCRIPTION}` - Brief summary of what you built
38- `{PLAN_OR_REQUIREMENTS}` - What it should do
39- `{BASE_SHA}` - Starting commit
40- `{HEAD_SHA}` - Ending commit
42**3. Act on feedback:**
43- Fix Critical issues immediately
44- Fix Important issues before proceeding
45- Note Minor issues for later
46- Push back if reviewer is wrong (with reasoning)

How to Request

1. Get git SHAs:

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

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)
Raw lines 24 to 47
Starts an agent Dispatch :32
Starts an agent subagent :32
Reads a file code-reviewer.md :34
48## Example
50```
51[Just completed Task 2: Add verification function]
53You: Let me request code review before proceeding.
55BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | cut -d' ' -f1)
56HEAD_SHA=$(git rev-parse HEAD)
58[Dispatch code reviewer subagent]
59 DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
60 PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
61 BASE_SHA: a7981ec
62 HEAD_SHA: 3df7661
64[Subagent returns]:
65 Strengths: Clean architecture, real tests
66 Issues:
67 Important: Missing progress indicators
68 Minor: Magic number (100) for reporting interval
69 Assessment: Ready to proceed
71You: [Fix progress indicators]
72[Continue to Task 3]
73```

Example

[Just completed Task 2: Add verification function]

You: Let me request code review before proceeding.

BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | cut -d' ' -f1)
HEAD_SHA=$(git rev-parse HEAD)

[Dispatch code reviewer subagent]
  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
  PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
  BASE_SHA: a7981ec
  HEAD_SHA: 3df7661

[Subagent returns]:
  Strengths: Clean architecture, real tests
  Issues:
    Important: Missing progress indicators
    Minor: Magic number (100) for reporting interval
  Assessment: Ready to proceed

You: [Fix progress indicators]
[Continue to Task 3]
Raw lines 48 to 74
Starts an agent Dispatch :58
Starts an agent subagent :58
Starts an agent Subagent :64
75## Common Rationalizations
77| Excuse | Reality |
78|--------|---------|
79| "I'll just review the diff myself instead of dispatching a reviewer" | You're the coordinator — reviewing the diff inline burns the context window you need to keep driving the work. Dispatch a reviewer subagent: the diff and the evaluation live in its context, and only the findings come back to you. |
80| "The reviewer needs my whole session history to understand the change" | Hand it precisely crafted context, never your session's history. That keeps the reviewer on the work product, not your thought process. |

Common Rationalizations

ExcuseReality
"I'll just review the diff myself instead of dispatching a reviewer"You're the coordinator — reviewing the diff inline burns the context window you need to keep driving the work. Dispatch a reviewer subagent: the diff and the evaluation live in its context, and only the findings come back to you.
"The reviewer needs my whole session history to understand the change"Hand it precisely crafted context, never your session's history. That keeps the reviewer on the work product, not your thought process.
Raw lines 75 to 81
Starts an agent dispatching :79
Starts an agent Dispatch :79
Starts an agent subagent :79
82## Red Flags
84**Never:**
85- Skip review because "it's simple"
86- Ignore Critical issues
87- Proceed with unfixed Important issues
88- Argue with valid technical feedback
90**If reviewer wrong:**
91- Push back with technical reasoning
92- Show code/tests that prove it works
93- Request clarification
95See template at: [code-reviewer.md](code-reviewer.md)

Red Flags

Never:

  • Skip review because "it's simple"
  • Ignore Critical issues
  • Proceed with unfixed Important issues
  • Argue with valid technical feedback

If reviewer wrong:

  • Push back with technical reasoning
  • Show code/tests that prove it works
  • Request clarification

See template at: code-reviewer.md

Raw lines 82 to 95
Reads a file code-reviewer.md :95

From obra/superpowers at 2ce8aa1, 2026-10-21. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.