Programming · Review & audit
requesting-code-review
/requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
For whom
- Author
- ehartye ↗
- Repository
- hartye-superpowers ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
Licence
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Original author description
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
How it works
- When to Request Review
- How to Request
- Example
- Integration with Workflows
- Hard Rules
Original SKILL.md headings · 107 lines, 411 words
SKILL.md preview
---
name: requesting-code-review
description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements
---
# Requesting Code Review
Dispatch code-reviewer agent 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 Agent tool with custom agent at `agents/code-reviewer.md`, fill template at `requesting-code-review/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
```
[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 code-reviewer agent via Agent tool]
WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/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
**Team-Driven Development:**
- Review after each task completion
- Reviewer agent provides feedback via SendMessage
- Implementer follows receiving-code-review discipline when handling feedback
**Executing Plans:**
- Review after all tasks complete, before finishing the branch
**Ad-Hoc Development:**
- Review before merge
- Review when stuck
## Hard Rules
Review catches issues while they're cheap to fix. Skipping it is a false economy:
- Don't skip review because "it's simple" — simple code ships bugs too
- Don't ignore Critical issues
- Don't proceed with unfixed Important issues
- When the feedback is technically valid, implement it — don't argue
**If the reviewer is wrong:**
- Push back with technical reasoning
- Show code or tests that prove the current approach works
- Ask for clarification if something is ambiguous
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 · ehartye/hartye-superpowers | 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 9a988dd07c5c (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
- 100ferrox-requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - 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.