Cursor Composer Task Delegate
Chachamaru127/claude-code-harness
Hands one implementation task to Cursor Composer in an isolated git worktree, then reviews its diff and cherry-picks the result into the main branch.
Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers.
Install Team Review
$ npx skills add NikiforovAll/claude-code-rules --skill team-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NikiforovAll/claude-code-rules team-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/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/handbook-code-review/skills/team-review .claude/skills/team-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 "team-review" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-code-review/skills/team-review into .claude/skills/team-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-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/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-code-review/skills/team-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 NikiforovAll/claude-code-rules --skill team-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NikiforovAll/claude-code-rules team-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/handbook-code-review/skills/team-review .agents/skills/team-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 "team-review" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-code-review/skills/team-review into .agents/skills/team-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-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 NikiforovAll/claude-code-rules --skill team-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NikiforovAll/claude-code-rules team-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/handbook-code-review/skills/team-review .cursor/skills/team-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 "team-review" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-code-review/skills/team-review into .cursor/skills/team-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-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/NikiforovAll/claude-code-rules.git --path plugins/handbook-code-review/skills/team-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 NikiforovAll/claude-code-rules --skill team-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NikiforovAll/claude-code-rules team-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/handbook-code-review/skills/team-review .gemini/skills/team-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 "team-review" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-code-review/skills/team-review into .gemini/skills/team-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-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 NikiforovAll/claude-code-rules team-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 NikiforovAll/claude-code-rules --skill team-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/handbook-code-review/skills/team-review .github/skills/team-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 "team-review" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-code-review/skills/team-review into .github/skills/team-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-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 NikiforovAll/claude-code-rules --skill team-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 NikiforovAll/claude-code-rules team-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/handbook-code-review/skills/team-review .opencode/skills/team-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 "team-review" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-code-review/skills/team-review into .opencode/skills/team-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-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
team-review- GitHub stars
- 141
- Token cost
- ~1.1k tokens
- SKILL.md length
- 542 words
- Files
- 1
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers.
- Works in 3 steps: Identify Changes → Create Review Team and Spawn Reviewers → Collect and Act on Findings
- Says team review
- SKILL.md covers Phase 1: Identify Changes, Phase 2: Create Review Team…, Phase 3: Collect and Act on… and Important
- Calls git
What it does
Team Review is an agent skill from NikiforovAll/claude-code-rules. Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. This skill should be used when the user says "team review", "review with team", or wants parallel code review with persistent team members for follow-up questions. Similar to /subagent-review but reviewers persist after review.
Its SKILL.md is about 1.1k 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, covering Code review and Subagents. It works with Git. The repository describes itself as: Learn practical techniques to enhance your AI-assisted development workflow with Claude Code. The licence is Apache-2.0.
When your agent uses it
- Says team review
- Review with team
- Wants parallel code review with persistent team members for follow-up questions
Example prompts
- “team review”
- “review with team”
- “/team-review”
Requirements
- Pre-approved tools (allowed-tools): Agent, Bash(git diff *), Bash(git log *), Bash(git status *), Read, Grep, Glob, TaskCreate, TaskUpdate, TaskList, TeamCreate, TeamDelete, SendMessage
Workflow steps
3 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 281c063. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
AgentBash(git diff *)Bash(git log *)Bash(git status *)ReadGrepGlobTaskCreateTaskUpdateTaskList
…and 3 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
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
Team Review loads about 1.1k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 542 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 NikiforovAll/claude-code-rules at commit 281c063, republished under its Apache-2.0 licence (© NikiforovAll). 542 words, ~1,058 tokens.
Download SKILL.mdSave it as
.claude/skills/team-review/SKILL.md (or your agent's skills folder).- name
- team-review
- description
- Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. This skill should be used when the user says "team review", "review with team", or wants parallel code review with persistent team members for follow-up questions. Similar to /subagent-review but reviewers persist after review.
- allowed-tools
- Agent, Bash(git diff *), Bash(git log *), Bash(git status *), Read, Grep, Glob, TaskCreate, TaskUpdate, TaskList, TeamCreate, TeamDelete, SendMessage
Team Review: Code Review with Persistent Team Members
Review all changed files for reuse, quality, and efficiency using a team of named reviewers that persist for follow-up questions.
Phase 1: Identify Changes
Run git diff (or git diff HEAD if there are staged changes) to see what changed. If there are no git changes, review the most recently modified files that the user mentioned or that you edited earlier in this conversation.
Store the full diff text — you will pass it to each reviewer.
Phase 2: Create Review Team and Spawn Reviewers
Create a team (or reuse an existing one) and spawn three named team members concurrently using the Agent tool. Each member gets the full diff as context.
Use run_in_background: true for all three so they run in parallel. Give each a descriptive name parameter.
Member 1: reuse-reviewer
Prompt: You are a code reuse reviewer. Here is the diff to review:
<paste full diff>For each change:
- Search for existing utilities and helpers that could replace newly written code. Look for similar patterns elsewhere in the codebase.
- Flag any new function that duplicates existing functionality. Suggest the existing function to use instead.
- Flag any inline logic that could use an existing utility — hand-rolled string manipulation, manual path handling, custom environment checks, ad-hoc type guards.
Report findings as a bulleted list. If the code is clean, say so.
Member 2: quality-reviewer
Prompt: You are a code quality reviewer. Here is the diff to review:
<paste full diff>Review for:
- Redundant state: state that duplicates existing state, cached values that could be derived
- Parameter sprawl: adding new parameters instead of generalizing
- Copy-paste with slight variation: near-duplicate code blocks
- Leaky abstractions: exposing internal details that should be encapsulated
- Stringly-typed code: using raw strings where constants or enums exist
- Unnecessary nesting: wrapper elements that add no value
- Unnecessary comments: comments explaining WHAT — delete; keep only non-obvious WHY
Report findings as a bulleted list. If the code is clean, say so.
Show full SKILL.md (211 more words)Show less
Member 3: efficiency-reviewer
Prompt: You are an efficiency reviewer. Here is the diff to review:
<paste full diff>Review for:
- Unnecessary work: redundant computations, repeated file reads, duplicate API calls, N+1 patterns
- Missed concurrency: independent operations run sequentially when they could be parallel
- Hot-path bloat: blocking work added to startup or per-request hot paths
- Recurring no-op updates: state updates that fire unconditionally — add change-detection guards
- Unnecessary existence checks: pre-checking before operating (TOCTOU anti-pattern)
- Memory: unbounded data structures, missing cleanup, event listener leaks
- Overly broad operations: reading entire files when only a portion is needed
Report findings as a bulleted list. If the code is clean, say so.
Phase 3: Collect and Act on Findings
Wait for all three reviewers to complete. Aggregate their findings and fix each issue directly. If a finding is a false positive or not worth addressing, note it and move on.
When done, briefly summarize what was fixed (or confirm the code was already clean).
Important
- Do NOT shut down the team after review — reviewers persist for follow-up questions
- Each reviewer should use
Bash(git diff),Read,Grep,Globto explore the codebase - Pass the
team_nameparameter when spawning agents so they join the same team - Create tasks for each reviewer to track progress
© NikiforovAll, Apache-2.0. 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 plugins/handbook-code-review/skills/team-review of NikiforovAll/claude-code-rules.
Open the folder on GitHubat commit 281c063
Compare with similar skills
Team 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 |
|---|---|---|---|---|---|---|
| Team Review this skillNikiforovAll/claude-code-rules | 141 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Cursor Composer Task DelegateChachamaru127/claude-code-harness | 3.2k | — | ~4.4k | Automated safety check: Notes | MIT | |
| Parallel Adversarial Change Reviewben-manes/caffeine | 18k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Parallel Specialist PR Reviewposhan0126/dotclaude | 870 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Code Revieweralirezarezvani/claude-code-tresor | 777 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Review And Simplify ChangesDimillian/Skills | 4k | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Parallel Adversarial Change Review
ben-manes/caffeine
Runs three parallel reviewers on a diff or branch, one blind, one design-aware and one matching past bug patterns, then triages their findings.
Parallel Specialist PR Review
poshan0126/dotclaude
Reviews a pull request, staged changes or a file by sending the diff to specialist reviewer agents in parallel, then merges their findings into one compact report.
Code Reviewer
alirezarezvani/claude-code-tresor
Automatic code quality and best practices analysis. An agent skill from alirezarezvani/claude-code-tresor.
Review And Simplify Changes
Dimillian/Skills
Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes.
Ad Review
CorridorTech/PoseCap
Two-axis fresh-context code review per WORKFLOW §10. An agent skill from CorridorTech/PoseCap.
More from NikiforovAll/claude-code-rules
All 26 skills in this repoReflect Solution
NikiforovAll/claude-code-rules
Summarize WHAT WAS SHIPPED in a Claude Code session as a self-contained HTML slide deck — the elevator pitch (problem, solution, decisions, artifacts, verification, gaps), not a play-by-play of tool…
Dotnet Analyzers
NikiforovAll/claude-code-rules
Run dotnet format to fix code style and analyzer diagnostics (IDE0005, CA, SA).
Ilspy Decompile
NikiforovAll/claude-code-rules
Understand implementation details of .NET code by decompiling assemblies.
Reflect Tree
NikiforovAll/claude-code-rules
Visualize a Claude Code session as a quest/skill tree — a navigable SVG graph where nodes are turns and edges show flow, with distinct visual encoding for normal flow, dead-ends, corrections…
Structured Plan Mode
NikiforovAll/claude-code-rules
This skill should be used when planning and tracking complex feature implementations that require systematic task decomposition.
Glab
NikiforovAll/claude-code-rules
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line.
Related
Works with
Categories
Questions about Team Review
What does Team Review do?
Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. Team Review is an agent skill from NikiforovAll/claude-code-rules. Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers.
When should I use Team Review?
Team Review fits situations like: says team review; review with team; wants parallel code review with persistent team members for follow-up questions.
How do I install Team Review in Claude Code?
Run `npx skills add NikiforovAll/claude-code-rules --skill team-review -a claude-code`. Or copy the skill folder (plugins/handbook-code-review/skills/team-review in NikiforovAll/claude-code-rules) into .claude/skills/team-review in your project. Claude Code loads it when a task matches its description.
How do I install Team Review in Codex?
Run `npx skills add NikiforovAll/claude-code-rules --skill team-review -a codex`. Or copy the skill folder (plugins/handbook-code-review/skills/team-review in NikiforovAll/claude-code-rules) into .agents/skills/team-review in your project. Codex loads it when a task matches its description.
Can I use Team 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 NikiforovAll/claude-code-rules --skill team-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/team-review, .gemini/skills/team-review, .github/skills/team-review and .opencode/skills/team-review in your project.
What does Team Review need to run?
Going by SKILL.md and its folder, Team Review needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Agent, Bash(git diff *), Bash(git log *), Bash(git status *), Read, Grep, Glob, TaskCreate, TaskUpdate, TaskList, TeamCreate, TeamDelete, SendMessage.
Does Team 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 Team 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 Team Review use?
Team Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Team Review use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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 Team Review?
Skills that share tags, products or a category with Team Review: Cursor Composer Task Delegate (Chachamaru127/claude-code-harness, 3.2k stars), Parallel Adversarial Change Review (ben-manes/caffeine, 18k stars), Parallel Specialist PR Review (poshan0126/dotclaude, 870 stars) and Code Reviewer (alirezarezvani/claude-code-tresor, 777 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Team Review?
NikiforovAll (a GitHub user) maintains it in NikiforovAll/claude-code-rules, which has 141 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 2, 2026.
Source: NikiforovAll/claude-code-rules on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.