swarmlisted

Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across the project," wants a comprehensive multi-angle code review, or asks what to fix first in a large or unfamiliar codebase. Also use for /swarm execute to have Claude fix the findings one at a time. Do NOT use this for a single-file review or a narrow bug fix — this skill is for repo-wide, multi-dimensional audits.
Zintellix/Claude-Skills · ★ 4 · AI & Automation · score 69

Install: claude install-skill Zintellix/Claude-Skills

# Claude Swarm Runs a parallel "swarm" of specialized subagents over a codebase, each scoped to a narrow category of issue, then synthesizes their raw findings into one deduplicated, severity-ranked action plan. Optionally executes fixes for approved findings. ## Commands - `/swarm audit [path]` — run the full audit (default path: repo root) - `/swarm status` — show the last audit summary from persisted state - `/swarm execute <severity|id>` — fix findings matching a severity tier (critical/high/medium/low) or a specific finding id - `/swarm show <id>` — show full detail for one finding ## State file All findings persist to `.claude/swarm-audit.json` at the repo root (create the `.claude/` dir if missing). This lets `/swarm execute` run in a later session without re-auditing, and lets `/swarm status` answer instantly. Always read this file first if it exists and the user references "the audit" or "findings" without re-running one. Schema for this file is in `references/output-schema.md`. ## `/swarm audit [path]` workflow 1. **Scope check.** If no path given, default to repo root, but if the repo is large (rough heuristic: >150 files or the user hasn't specified), ask the user to confirm scope or suggest a subdirectory. Don't silently audit a massive monorepo — cost and time scale with size. 2. **Spawn the five audit agents in parallel.** Use a single message with five Task tool calls so they genuinely run concurrently. For each, read the corresponding