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.
Review the current branch with six specialist lenses (security, correctness, conventions, tests, architecture, duplication), then put every finding through an adversarial verifier that tries to…
Install Squad Review
$ npx skills add nicknisi/claude-plugins --skill squad-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nicknisi/claude-plugins squad-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/nicknisi/claude-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/essentials/skills/squad-review .claude/skills/squad-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 "squad-review" agent skill from https://github.com/nicknisi/claude-plugins/tree/main/plugins/essentials/skills/squad-review into .claude/skills/squad-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squad-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/nicknisi/claude-plugins/tree/main/plugins/essentials/skills/squad-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 nicknisi/claude-plugins --skill squad-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nicknisi/claude-plugins squad-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicknisi/claude-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/essentials/skills/squad-review .agents/skills/squad-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 "squad-review" agent skill from https://github.com/nicknisi/claude-plugins/tree/main/plugins/essentials/skills/squad-review into .agents/skills/squad-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squad-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 nicknisi/claude-plugins --skill squad-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nicknisi/claude-plugins squad-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicknisi/claude-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/essentials/skills/squad-review .cursor/skills/squad-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 "squad-review" agent skill from https://github.com/nicknisi/claude-plugins/tree/main/plugins/essentials/skills/squad-review into .cursor/skills/squad-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squad-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/nicknisi/claude-plugins.git --path plugins/essentials/skills/squad-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 nicknisi/claude-plugins --skill squad-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nicknisi/claude-plugins squad-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicknisi/claude-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/essentials/skills/squad-review .gemini/skills/squad-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 "squad-review" agent skill from https://github.com/nicknisi/claude-plugins/tree/main/plugins/essentials/skills/squad-review into .gemini/skills/squad-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squad-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 nicknisi/claude-plugins squad-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 nicknisi/claude-plugins --skill squad-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nicknisi/claude-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/essentials/skills/squad-review .github/skills/squad-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 "squad-review" agent skill from https://github.com/nicknisi/claude-plugins/tree/main/plugins/essentials/skills/squad-review into .github/skills/squad-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squad-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 nicknisi/claude-plugins --skill squad-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 nicknisi/claude-plugins squad-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nicknisi/claude-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/essentials/skills/squad-review .opencode/skills/squad-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 "squad-review" agent skill from https://github.com/nicknisi/claude-plugins/tree/main/plugins/essentials/skills/squad-review into .opencode/skills/squad-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squad-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
squad-review- GitHub stars
- 114
- Token cost
- ~751 tokens
- SKILL.md length
- 349 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review the current branch with six specialist lenses (security, correctness, conventions, tests, architecture, duplication), then put every finding through an adversarial verifier that tries to…
- The user asks for a thorough
- SKILL.md covers Run it, Pick the scope yourself, Report the result and Requirements
- Runs JavaScript scripts from its folder; calls git
- Paranoid review
What it does
Squad Review is an agent skill from nicknisi/claude-plugins. Review the current branch with six specialist lenses (security, correctness, conventions, tests, architecture, duplication), then put every finding through an adversarial verifier that tries to refute it — so what reaches you has already survived a skeptic. Use when the user asks for a thorough, deep, or paranoid review, a review before merging or shipping, a "real" review, or wants to know what a review would catch that a quick pass misses. Costs 12 agents; for a fast single-pass read, use the built-in…
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/workflow.js`).
It sits in Development. It works with Git. The repository describes itself as: Nick's own marketplace of Claude Plugins. The licence is MIT.
When your agent uses it
- The user asks for a thorough
- Paranoid review
- A review before merging
- Wants to know what a review would catch that a quick pass misses
Example prompts
- “/squad-review”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 6a6decd. 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
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
Squad Review loads about 751 tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 349 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); the scripts in this folder are not scanned.
SKILL.md
The full file from nicknisi/claude-plugins at commit 6a6decd, republished under its MIT licence (© nicknisi). 349 words, ~751 tokens.
Download SKILL.mdSave it as
.claude/skills/squad-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- squad-review
- description
- Review the current branch with six specialist lenses (security, correctness, conventions, tests, architecture, duplication), then put every finding through an adversarial verifier that tries to refute it — so what reaches you has already survived a skeptic. Use when the user asks for a thorough, deep, or paranoid review, a review before merging or shipping, a "real" review, or wants to know what a review would catch that a quick pass misses. Costs 12 agents; for a fast single-pass read, use the built-in code-review skill instead.
- argument-hint
- Optional — what to review (defaults to the branch diff vs main)
Squad Review
Six lenses in parallel, each finding then attacked by a verifier that assumes it is wrong until proven otherwise. The verification is the point: an unverified fan-out produces six sections of plausible noise, and you stop reading it by the third review.
Run it
Resolve the script path, then hand it to the Workflow tool:
echo ${CLAUDE_PLUGIN_ROOT}/skills/squad-review/scripts/workflow.jsWorkflow({
scriptPath: "<the path printed above>",
args: { scope: "<git command>", label: "<human description>" }
})Pick the scope yourself
Read the git state and choose — do not open a menu:
- On a feature branch with commits →
git diff main...HEAD(the normal case) - On main, or a branch with only uncommitted work →
git diff HEAD - Untracked files present and relevant → name them in
labelso reviewers read them in full; a diff won't show them - Nothing to review → say so and stop, don't launch the workflow
Ask only when two scopes both have substantial content and you genuinely can't tell which one the user means. If the user named a scope, use it.
Report the result
findings are ranked and already verified. Present them grouped by severity, not
by lens — the lens is metadata, not structure. Lead with blockers. Give each
finding its file:line, what breaks, and the fix direction.
Three fields decide whether the review can be trusted, and all three must reach the user:
refuted— say how many and why, in one line. That number is the evidence verification happened. Hiding it makes this look like every other review.unverified— findings whose verifier never ruled on them. Report them under a separate heading that says exactly that. They have not survived a skeptic, so never merge them into the findings list.lenses_failed— non-empty means the review is incomplete. Name the lenses that died. Never present a partial review as a clean bill of health.
Do not re-rank or soften what the verifiers confirmed, and do not write the report to a file unless asked.
Requirements
Needs Claude Code's Workflow tool. This skill also ships to Pi via the repo's
pi.skills glob, where that tool does not exist — there it will not run, and
that is the intended failure rather than a silent degradation to something
weaker.
© nicknisi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in plugins/essentials/skills/squad-review of nicknisi/claude-plugins.
- SKILL.md
- scripts/workflow.js
Open the folder on GitHubat commit 6a6decd
Compare with similar skills
Squad 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 |
|---|---|---|---|---|---|---|
| Squad Review this skillnicknisi/claude-plugins | 114 | — | ~751 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Finishing A Development Branchfarm-fe/farm | 5.6k | 35 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
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.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
- Official
Doc Sync
JetBrains/ideavim
Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.
More from nicknisi/claude-plugins
All 12 skills in this repoBlog Post Writer
nicknisi/claude-plugins
Turn Nick Nisi's raw material into a blog post draft in his voice.
Image Gen
nicknisi/claude-plugins
Generate or edit images via Google Gemini (nano-banana-pro) or OpenAI gpt-image-2.
Prototype
nicknisi/claude-plugins
Build a throwaway prototype to answer a design question before committing to real implementation.
Tmux
nicknisi/claude-plugins
Read and drive other tmux panes when Claude runs inside tmux.
Youtube Notes
nicknisi/claude-plugins
Pull captions from a YouTube video and turn them into chapter-aligned notes where every claim carries a clickable timestamp.
Conference Talk Builder
nicknisi/claude-plugins
Create conference talk outlines and slide-by-slide content plans using narrative frameworks.
Related
Works with
Categories
Questions about Squad Review
What does Squad Review do?
Review the current branch with six specialist lenses (security, correctness, conventions, tests, architecture, duplication), then put every finding through an adversarial verifier that tries to…. Squad Review is an agent skill from nicknisi/claude-plugins. Review the current branch with six specialist lenses (security, correctness, conventions, tests, architecture, duplication), then put every finding through an adversarial verifier that tries to refute it — so what reaches you has already survived a skeptic.
When should I use Squad Review?
Squad Review fits situations like: the user asks for a thorough; paranoid review; A review before merging; wants to know what a review would catch that a quick pass misses.
How do I install Squad Review in Claude Code?
Run `npx skills add nicknisi/claude-plugins --skill squad-review -a claude-code`. Or copy the skill folder (plugins/essentials/skills/squad-review in nicknisi/claude-plugins) into .claude/skills/squad-review in your project. Claude Code loads it when a task matches its description.
How do I install Squad Review in Codex?
Run `npx skills add nicknisi/claude-plugins --skill squad-review -a codex`. Or copy the skill folder (plugins/essentials/skills/squad-review in nicknisi/claude-plugins) into .agents/skills/squad-review in your project. Codex loads it when a task matches its description.
Can I use Squad 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 nicknisi/claude-plugins --skill squad-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/squad-review, .gemini/skills/squad-review, .github/skills/squad-review and .opencode/skills/squad-review in your project.
What does Squad Review need to run?
Going by SKILL.md and its folder, Squad Review needs JavaScript for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: Node.js.
Does Squad Review access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Squad 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Squad Review use?
Squad 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 Squad Review use?
About 751 tokens (SKILL.md is roughly 3k 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 Squad Review?
Skills that share tags, products or a category with Squad Review: Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Finishing A Development Branch (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Squad Review?
nicknisi (a GitHub user) maintains it in nicknisi/claude-plugins, which has 114 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 11, 2026.
Source: nicknisi/claude-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.