# swarm-issue

swarm-issue is a Claude Code command that connects GitHub Issues to swarm work by splitting tasks into subtasks, suggesting agents, and tracking progress. It supports workflows managed through GitHub Issues.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 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/commands/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/commands/swarm-issue

## What it does

The command uses an issue’s content to prepare work for a swarm: it can analyze the task, suggest agents, and split work into subtasks. The examples use `gh` to read and edit GitHub Issues, while swarm operations run through `npx ruv-swarm`. Issue comments can also trigger actions such as analysis or task estimation.

Results can be written back to GitHub: add a subtask checklist, create linked issues for high-priority work, or post a progress summary. The guide also shows GitHub Actions automation and project-board syncing. You need a configured `gh` installation for the GitHub read and edit steps; those steps cannot run without it.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/swarm-issue.md` — Call it with /swarm-issue. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/swarm-issue.md` — Call it with /prompts:swarm-issue. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/swarm-issue.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/swarm-issue.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

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/commands/github/swarm-issue.md

## When to use it
- Break a GitHub Issue into prioritized subtasks
- Suggest agents based on issue content
- Update an issue checklist with swarm progress
- Create linked issues for high-priority subtasks
- Sync issue status with a project board

## Example prompts
- Break Issue `456` into subtasks and add a checklist to its description.
- Analyze Issue `456`, suggest agents, and estimate its complexity.
- Refresh progress for Issue `456` and post a summary comment.

## Similar
- [oss-contributor-swarm](https://affpapa.org/en/nevibecode/skills/oss-contributor-swarm.md) — skill · ★ 138 repo stars
- [github-project-management](https://affpapa.org/en/nevibecode/skills/github-project-management.md) — skill · 1400 installs
- [issue-label](https://affpapa.org/en/nevibecode/skills/issue-label.md) — skill · 206 installs
- [linear-task-to-issue](https://affpapa.org/en/nevibecode/commands/linear-task-to-issue.md) — command · 129 installs
- [resolve-issue](https://affpapa.org/en/nevibecode/skills/resolve-issue.md) — skill · 1200 installs
- [issue-tracker](https://affpapa.org/en/nevibecode/skills/issue-tracker.md) — skill · 795 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
