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
- HarmAalbers ↗
- Repository
- claude-requirements-framework ↗
- Licence
- MIT
- Last repository change
- 09.10.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
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 09.10.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
- Integration with Workflows
- Requirements Integration
- Red Flags
Original SKILL.md headings · 87 lines, 313 words
SKILL.md preview
---
name: requesting-code-review
description: Use when completing tasks, implementing major features, or before merging to verify work meets requirements
git_hash: 307b927
---
# Requesting Code Review
Dispatch code review to catch issues before they cascade. Uses our specialized review agents or `/pre-commit` command.
**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
### Option 1: Use `/pre-commit` (Recommended)
Our framework provides specialized review agents. Simply run:
```
/pre-commit
```
This dispatches code-reviewer, silent-failure-hunter, and tool-validator agents with cross-validation.
### Option 2: Manual Review via Subagent
**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 `requirements-framework:code-reviewer` type, fill template at `references/code-reviewer-template.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)
## 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
## Requirements Integration
When this skill completes, it auto-satisfies the `pre_commit_review` requirement (deprecated since v2.6, disabled by default). The `/pre-commit` command remains available for voluntary use.
## 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
Files in this package (3)
- SKILL.md 2 KB
- SKILL.md.j2 2 KB
- references/code-reviewer-template.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · HarmAalbers/claude-requirements-framework | 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 9714194e1fe1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 2 · 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. - 100audit-review
Use when completing tasks, implementing major features, or before merging — dispatches the-inspector to audit the books before the job is closed