AgentAlley

Skills · Coding

Requesting Code Review

Unverified●30/40

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

Originally by obra · MIT

Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor·UnknownWe have not crawled the repo tree, so we will not guess
Codex·UnknownWe have not crawled the repo tree, so we will not guess
Gemini CLI·UnknownThe spec defines no detection rule for Gemini
Copilot·UnknownWe have not crawled the repo tree, so we will not guess
npx agentalley add requesting-code-review

This command does not work yet — the CLI is still being built. Until then, use Raw in the reader below to take the file.

Who is stuck, and on what

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

The whole source

No sign-in, no blur, nothing truncated
requesting-code-review/SKILL.md96 lines2.9 KBRawView on GitHub
Frontmatter — 2 properties
namerequesting-code-review
descriptionUse when completing tasks, implementing major features, or before merging to verify work meets requirements
1---
2name: requesting-code-review
3description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements
4---A5 — No allowed-tools declared — no way to tell what this skill may touch
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.
11 
12## When to Request Review
13 
14**Mandatory:**
15- After each task in subagent-driven development
16- After completing major feature
17- Before merge to main
18 
19**Optional but valuable:**
20- When stuck (fresh perspective)
21- Before refactoring (baseline check)
22- After fixing complex bug
23 
24## How to Request
25 
26**1. Get git SHAs:**
27```bash
28BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
29HEAD_SHA=$(git rev-parse HEAD)
30```
31 
32**2. Dispatch code reviewer subagent:**
33 
34Dispatch a `general-purpose` subagent, filling the template at [code-reviewer.md](code-reviewer.md)
35 
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
41 
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)
47 
48## Example
49 
50```
51[Just completed Task 2: Add verification function]
52 
53You: Let me request code review before proceeding.
54 
55BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
56HEAD_SHA=$(git rev-parse HEAD)
57 
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
63 
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
70 
71You: [Fix progress indicators]
72[Continue to Task 3]
73```
74 
75## Common Rationalizations
76 
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. |
81 
82## Red Flags
83 
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
89 
90**If reviewer wrong:**
91- Push back with technical reasoning
92- Show code/tests that prove it works
93- Request clarification
94 
95See template at: [code-reviewer.md](code-reviewer.md)
96 

Reviews

Installed this one?Write the first review and take the Trailblazer badge.

Reviews only open after a real install, so this is empty — and we leave it empty rather than invent one.

Alternatives

Also in Coding
Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current sessionCoding · MIT◐◐◐◐◐●36/40Python Code Style & DocumentationPython code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.Coding · MIT◐····●35/40Competitor Price Analysis 💲Competitor pricing strategy analysis and market positioning. Price mapping, pricing gaps identification, elasticity signals evaluation, and strategic pricing optimization. Use when the user asks about competitor pricing, price analysis, pricing strategy, or coCoding · MIT◐····●34/40Competitor Price Tracker 📊Set up competitor price tracking and monitoring workflows. Track price changes, detect promotions, analyze pricing patterns, and get alerts for competitive price movements.Coding · MIT◐····●34/40