# swarm-issue

swarm-issue turns a GitHub issue into work for a swarm: splits it into subtasks, assigns agents and reports progress back inside the issue.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 850 repo stars
- Author: ruvnet
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ruvnet/agentic-flow/tree/HEAD/.claude/agents/github/swarm-issue.md
- Updated: 2026-10-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/swarm-issue

## What it does

The agent pulls an issue in full, title and body and labels and comments, then cuts the job into prioritised subtasks and hands each one to an agent. Results land where the team already looks: a checklist edited into the issue body, a status comment, labels updated as pieces close.

Two hooks bracket the run. One sets up coordination before work starts and parks issue metadata in swarm memory; the other posts a report afterwards and opens follow-up tasks. Most of its tool list is MCP methods such as `mcp__github__get_issue`, `mcp__github__update_issue`, `mcp__claude-flow__agent_spawn` and `mcp__claude-flow__memory_usage`, with `Bash`, `Grep`, `Read`, `Write` and the Todo tools alongside. The documented workflows lean on the `npx ruv-swarm` CLI and `gh`.

Both MCP servers, `github` and `claude-flow`, have to be connected first. Leave one out and its tools never resolve, so the agent stalls on its first call.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/swarm-issue.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/swarm-issue.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/swarm-issue.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ruvnet/agentic-flow/tree/HEAD/.claude/agents/github/swarm-issue.md

## When to use it
- split a big issue into prioritised subtasks
- pick agents from labels and issue text
- keep the issue checklist matching real progress
- link child issues back to the parent one
- post a swarm progress summary as one comment

## Example prompts
- Break issue #456 into subtasks and assign an agent to each.
- Start a swarm for issue #456 and track progress in the issue body.
- Check what is still open on issue #456 and refresh the labels.

## Similar
- [oss-contributor-swarm](https://affpapa.org/en/nevibecode/skills/oss-contributor-swarm.md) — skill · ★ 138 repo stars
- [dyad:swarm-pr-review](https://affpapa.org/en/nevibecode/skills/dyadswarm-pr-review.md) — skill · ★ 22348 repo stars
- [github-project-management](https://affpapa.org/en/nevibecode/skills/github-project-management.md) — skill · 1400 installs
- [gitnexus-pr-swarm-review](https://affpapa.org/en/nevibecode/skills/gitnexus-pr-swarm-review.md) — skill · 438 installs
- [om-auto-fix-issue](https://affpapa.org/en/nevibecode/skills/om-auto-fix-issue.md) — skill · 4700 installs
- [github-code-review](https://affpapa.org/en/nevibecode/skills/github-code-review.md) — skill · 1300 installs

From the same set: [ruvnet/agentic-flow](https://affpapa.org/en/nevibecode/by/ruvnet/agentic-flow.md) — 76 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
