Request Review
Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes. The reviewer has no shared state with the coding agent and gives a genuine second opinion. Use after audit-code passes, before committing, or when user wants an independent code review.
Install
npx skills add danielvm-git/bigpowers --skill request-reviewgit clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/request-review ~/.claude/skills/request-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Request Review Dispatch fresh reviewer agents with clean contexts. Reviewers have no shared state — they find what the coding agent missed. ## Target (argument) If an argument was passed after `/request-review` (e.g. `/request-review abc1234` or `/request-review HEAD~3..HEAD`), use it as the diff target when building the reviewer brief: ```bash git diff <arg> # range: abc..def, HEAD~3..HEAD git show <arg> # single commit: abc1234 ``` If no argument was given, review uncommitted working-tree changes. **Distinct from `audit-code`:** `audit-code` is self-review (internal). This skill dispatches external agents. **Solo developer note:** Reviewer agents replace the human reviewer. **Run `audit-code` first.** Don't waste reviewer attention on hygiene issues you could have caught yourself. ## Santa Method — Dual-Blind AND Gate (e45s07) Use **two independent reviewers** (Reviewer A and Reviewer B) with **no shared context** between them or the coding agent. | Parameter | Value | |-----------|-------| | Reviewers | 2 (mandatory) | | `MAX_REVIEW_ITERATIONS` | **5** (hard cap — e45s28; iteration 6 forbidden) | | Pass rule | **AND-gate** — both reviewers must pass independently | | Blindness | Neither reviewer sees the other's report until both complete | **Iteration loop (max `MAX_REVIEW_ITERATIONS`):** 1. Dispatch Reviewer A and Reviewer B in parallel with identical briefs but separate contexts.
Details
- Skill name
request-review- Repository
- danielvm-git/bigpowers
- Path
.cline/skills/request-review/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Request Review skill do?
Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes. The reviewer has no shared state with the coding agent and gives a genuine second opinion. Use after audit-code passes, before committing, or when user wants an independent code review.
How do I install the Request Review skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill request-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Request Review popular?
It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.
Related skills
Align Grid
292danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i
Assess Impact
292danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".
Audit Code
292danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Trace Requirement
292danielvm-git/bigpowers
Link story IDs from specs/release-plan.yaml + epic capsule directories to the implementing code and tests. Produces specs/TRACEABILITY_LATEST.md. Use when you want to verify coverage of a release plan, audit which stories are implemented, or find "dark" stories with no code.
Plan Refactor
292danielvm-git/bigpowers
Create a detailed refactor plan with tiny commits via user interview, then save it as specs/REFACTOR_LATEST.md. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
CLI Audit
115crafter-station/skills
Audit an existing CLI against cli-build: how well an agent can operate it and how well a human can read it. Use when the user wants to audit a CLI, check whether a tool is agent-first, find out what a published CLI got wrong, grade a CLI's human output, verify that named safety features are actually wired, or prepare a patch list before improving an existing command-line tool. Reports findings with evidence; it does not patch.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.