Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes.
Install Request Review
$ npx skills add danielvm-git/bigpowers --skill request-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install danielvm-git/bigpowers request-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/request-review .claude/skills/request-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "request-review" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/request-review into .claude/skills/request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/danielvm-git/bigpowers/tree/main/skills/request-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add danielvm-git/bigpowers --skill request-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install danielvm-git/bigpowers request-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/request-review .agents/skills/request-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "request-review" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/request-review into .agents/skills/request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add danielvm-git/bigpowers --skill request-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install danielvm-git/bigpowers request-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/request-review .cursor/skills/request-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "request-review" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/request-review into .cursor/skills/request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/danielvm-git/bigpowers.git --path skills/request-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add danielvm-git/bigpowers --skill request-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install danielvm-git/bigpowers request-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/request-review .gemini/skills/request-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "request-review" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/request-review into .gemini/skills/request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install danielvm-git/bigpowers request-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add danielvm-git/bigpowers --skill request-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/request-review .github/skills/request-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "request-review" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/request-review into .github/skills/request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add danielvm-git/bigpowers --skill request-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install danielvm-git/bigpowers request-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/request-review .opencode/skills/request-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "request-review" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/request-review into .opencode/skills/request-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
request-review- GitHub stars
- 256
- Token cost
- ~1.4k tokens
- SKILL.md length
- 525 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes.
- Works in 4 steps: Prepare the review brief → Fan-out parallel reviewers (e45s17) → Collect both reports → …
- Wants an independent code review
- SKILL.md covers Santa Method — Dual-Blind AND…, Process and Verify
- Calls npm
What it does
Request Review is an agent skill from danielvm-git/bigpowers. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: Agent skills synthesizing years of software engineering discipline into a prescriptive methodology for solo developers. The licence is MIT.
When your agent uses it
- Wants an independent code review
Example prompts
- “/request-review”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 812d57a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Request Review loads about 1.4k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 525 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from danielvm-git/bigpowers at commit 812d57a, republished under its MIT licence (© danielvm-git). 525 words, ~1,397 tokens.
Download SKILL.mdSave it as
.claude/skills/request-review/SKILL.md (or your agent's skills folder).- name
- request-review
- description
- 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.
- model
- opus
- effort
- standard
story: e45s28
Request Review
Dispatch fresh reviewer agents with clean contexts. Reviewers have no shared state — they find what the coding agent missed.
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):
- Dispatch Reviewer A and Reviewer B in parallel with identical briefs but separate contexts.
- Collect both reports. Each categorizes findings: must-fix / should-fix / consider.
- AND-gate: If either reviewer has must-fix findings → FAIL round. Run
respond-review, fix, re-dispatch both reviewers. - If both pass (zero must-fix, score ≥ 94% each) → review complete.
- After 5 iterations without dual pass → stop; report "Review cap exhausted (5/5). Human decision required." Do not merge.
HARD GATE — Single-reviewer pass is insufficient. Partial agreement does not satisfy the AND-gate.
Process
1. Prepare the review brief
Write a self-contained brief for each reviewer. Include:
- What was built (feature description, not implementation)
- Which files changed (the diff context)
- What
specs/artifacts are relevant (activeepics/eNN-*.yaml,requirements/SCOPE_LATEST.yaml,bugs/BUG-*.md) - What CONVENTIONS.md requires
- What the verify command is
- What you're most uncertain about (where you want fresh eyes)
- Security focus — If the epic has a
specs/security/epics/<id>/THREAT_MODEL.md, include the relevant vulnerability categories as reviewer focal points. Also include the false-positive exclusion rules so the reviewer avoids known-safe patterns. Tag the review assecurity-sensitive: trueif THREAT_MODEL risk is HIGH+.
Show full SKILL.md (228 more words)Show less
2. Fan-out parallel reviewers (e45s17)
Beyond the mandatory dual-blind pair (e45s07), optionally dispatch N dimension-specific subagents in one message — one check per agent for broader coverage (OpenAI Codex code-review-* pattern):
| Agent | Focus |
|---|---|
| R-correctness | Logic, edge cases, verify command result |
| R-conventions | CONVENTIONS.md, test quality (F.I.R.S.T) |
| R-security | Injection, auth, secrets (when security-sensitive) |
| R-design | Simpler alternatives, API shape |
Santa Method still applies: each agent is blind; AND-gate uses Reviewer A + B scores. Fan-out agents feed findings into respond-review but do not replace the dual-blind pair.
2b. Dispatch both reviewer agents (parallel)
Use the Agent tool twice with completely fresh contexts. Each prompt must be self-contained — no references to "our conversation" or "what we discussed."
You are code reviewer [A|B]. Review the following code changes independently.
Context: [feature description]
CONVENTIONS.md rules: [paste relevant sections]
Active epic shard: [paste or summarize from specs/epics/]
Diff: [paste git diff or describe changed files]
Verify command: [runnable command]
Review for:
1. Correctness — does the code do what was intended?
2. CONVENTIONS.md compliance — are all rules followed?
3. Test quality — do tests verify behavior (not implementation)?
4. Design — are there simpler or more robust approaches?
5. Edge cases — what inputs or states could cause failures?
6. Security — any injection, auth, or data exposure risks?
7. Refactoring smells — explicitly name any detected Fowler smells: Mysterious Name, Duplicated Code, Feature Envy, Data Clumps, Primitive Obsession, Message Chains, Middle Man
For each finding, categorize as: must-fix / should-fix / consider.
Run the verify command and report the result.3. Collect both reports
When reviewers return:
- Read every finding from both reports before acting on any
- Note each verify command result
- Compute quality score per reviewer:
100 × (total_items − must_fix − should_fix) / total_items - AND-gate check: both scores ≥ 94% and zero must-fix from both?
HARD GATE — If either score < 94% or either has must-fix → FAIL round. Run
respond-reviewfirst. The 94% threshold also applies tonpm run compliance(scripts/audit-compliance.sh).
4. Hand off to respond-review
Pass combined findings to respond-review to categorize and apply fixes. Increment iteration counter. Re-dispatch both reviewers until AND-gate passes or iteration 3 exhausted.
Report to user: "Review round [N/3]. Reviewer A: [score], Reviewer B: [score]. AND-gate: [PASS|FAIL]."
Verify
→ verify: test -f scripts/lib/parallel-review-worktrees.sh && test -f skills/request-review/SKILL.md
© danielvm-git, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/request-review of danielvm-git/bigpowers.
Open the folder on GitHubat commit 812d57a
Compare with similar skills
Request Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Request Review this skilldanielvm-git/bigpowers | 256 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from danielvm-git/bigpowers
All 39 skills in this repoExtract Design
danielvm-git/bigpowers
Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose.
Align Grid
danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one.
Assess Impact
danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written.
Audit Code
danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer.
Audit Plan
danielvm-git/bigpowers
Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY/NOT READY verdict before engagement begins.
Compose Workflow
danielvm-git/bigpowers
Chain multiple bigpowers skills into a custom workflow recipe saved in specs/.
Related
Categories
Questions about Request Review
What does Request Review do?
Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes. Request Review is an agent skill from danielvm-git/bigpowers. Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes.
When should I use Request Review?
Request Review fits situations like: wants an independent code review.
How do I install Request Review in Claude Code?
Run `npx skills add danielvm-git/bigpowers --skill request-review -a claude-code`. Or copy the skill folder (skills/request-review in danielvm-git/bigpowers) into .claude/skills/request-review in your project. Claude Code loads it when a task matches its description.
How do I install Request Review in Codex?
Run `npx skills add danielvm-git/bigpowers --skill request-review -a codex`. Or copy the skill folder (skills/request-review in danielvm-git/bigpowers) into .agents/skills/request-review in your project. Codex loads it when a task matches its description.
Can I use Request Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add danielvm-git/bigpowers --skill request-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/request-review, .gemini/skills/request-review, .github/skills/request-review and .opencode/skills/request-review in your project.
What does Request Review need to run?
Going by SKILL.md and its folder, Request Review needs the command-line tools its instructions call (npm).
Does Request Review access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Request Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Request Review use?
Request Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Request Review use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Request Review?
Skills that share tags, products or a category with Request Review: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Request Review?
danielvm-git (a GitHub user) maintains it in danielvm-git/bigpowers, which has 256 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 21, 2026.
Source: danielvm-git/bigpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.