Agent skill · software engineering · sickn33
review-swarm
Parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps.
Why this skill is useful
Adds a structured multi-agent review process for git diffs that enhances the AI's capability to identify complex issues like behavioral regressions and security risks.
What it needs
Requires git installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Review Swarm When to Use Use this skill when you need parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps. Use when the user asks for a review swarm, parallel review, diff review,... Review a diff with four read-only sub-agents in parallel, then have the main agent filter, order, and summarize only the issues that matter. This skill is review-only: sub-agents do not edit files, and the main agent does not apply fixes as part of this workflow. Step 1: Determine Scope and Intent Prefer this scope order: 1. Files or paths explicitly named by the user 2. Current git changes 3. An explicit branch, commit, or PR diff requested by the user 4. Most recently modified tracked files, only if the user asked for a review and there is no clearer diff If there is no clear review scope, stop and say so briefly. When using git changes, choose the smallest correct diff command: unstaged work: git diff staged work: git diff --cached mixed staged and unstaged work: review both explicit branch or commit comparison: use exactly what the user requested Before launching reviewers, read the closest local instructions and any relevant project docs for the touched area, such as: AGENTS.md repo workflow docs architecture or contract docs for the touched module Build a short intent packet for the reviewers: 1. What behavior is meant to change 2. What behavior should remain unchanged 3. Any stated or inferred constraints, such as compatibility, rollout, security, or migration expectations If the user did not state the intent clearly, infer it from the diff and say that the inference may be incomplete. Step 2: Launch Four Read-Only Reviewers in Parallel Launch four sub-agents when the scope is large enough for parallel review to help. For a tiny diff or one very small file, it is acceptable to review locally instead. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/review-swarm--bfebb7