requesting-code-review
/requesting-code-review
Lightweight standalone code review workflow. Use for ad-hoc reviews outside structured development workflows—after completing single tasks, before merging to main, or when stuck and needing a fresh perspective. For structured multi-task development, use subagent-driven-development instead (which includes integrated review stages).
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 02.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Lightweight standalone code review workflow. Use for ad-hoc reviews outside structured development workflows—after completing single tasks, before merging to main, or when stuck and needing a fresh perspective. For structured multi-task development, use subagent-driven-development instead (which includes integrated review stages).
Original author description
Lightweight standalone code review workflow. Use for ad-hoc reviews outside structured development workflows—after completing single tasks, before merging to main, or when stuck and needing a fresh perspective. For structured multi-task development, use subagent-driven-development instead (which includes integrated review stages).
How it works
- When to Request Review
- How to Request
- Example
- Integration with Workflows
- Red Flags
SKILL.md preview
---
name: requesting-code-review
description: Lightweight standalone code review workflow. Use for ad-hoc reviews outside structured development workflows—after completing single tasks, before merging to main, or when stuck and needing a fresh perspective. For structured multi-task development, use subagent-driven-development instead (which includes integrated review stages).
---
# Requesting Code Review
Dispatch superpowers:code-reviewer subagent to catch issues before they cascade.
**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 origin/main
HEAD_SHA=$(git rev-parse HEAD)
```
**2. Dispatch code-reviewer subagent:**
Use Task tool with superpowers:code-reviewer type, fill template at `code-reviewer.md`
**Placeholders:**
- `{WHAT_WAS_IMPLEMENTED}` - What you just built
- `{PLAN_OR_REQUIREMENTS}` - What it should do
- `{BASE_SHA}` - Starting commit
- `{HEAD_SHA}` - Ending commit
- `{DESCRIPTION}` - Brief summary
**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)
## Example
```text
[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 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)
[Dispatch superpowers:code-reviewer subagent]
WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
PLAN_OR_REQUIREMENTS: Task 2 from docs/plans/deployment-plan.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
[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]
```
## Integration with Workflows
**Subagent-Driven Development:**
- Review after EACH task
- Catch issues before they compound
- Fix before moving to next task
**Executing Plans:**
- Review after each batch (3 tasks)
- Get feedback, apply, continue
**Ad-Hoc Development:**
- Review before merge
- Review when stuck
## 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: requesting-code-review/code-reviewer.md
Files in this package (2)
- SKILL.md 3 KB
- code-reviewer.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jr2804/prompts | 100 | MIT |
| GanyuanRan/Aegis | 100 | MIT |
| event4u-app/agent-config | 100 | MIT |
| osmontero/opencode-skills | 100 | MIT |
| jjuraszek/pi-gauntlet | 100 | MIT |
| seaworld008/commonly-used-high-value-skills | 100 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| nikospavlopoulos/devops-mutant-powers | 100 | MIT |
| coco-research/coco | 100 | MIT |
Database snapshot: 13.11.2026 · package version a04fbc2d73bf (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100subagent-driven-development
Structured multi-task development workflow with integrated two-stage review (spec compliance + code quality). Use when executing implementation plans in the CURRENT session with independent tasks. Dispatches fresh subagent per task with built-in review gates. For ad-hoc single… - 100sr-requesting-code-review
Use when the user explicitly requests a code review, or during subagent-driven development where review is part of the workflow - 100workthrough
Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation. - 100requesting-code-review-codex
Request a high-signal Codex-backed review of a diff or task result. Use when completing tasks, implementing major features, or before merging. Codex-backed variant.