Skip to main content
command CX Codex

swarm-issue — Claude Code command for GitHub Issues

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.

no license ★ 850 updated 2026-10-26

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/swarm-issue.md
Open on GitHub

What swarm-issue 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.

What it helps with

  • 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 for the agent

  • 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.

How to install swarm-issue

Manually: put the files in place

.claude/commands/swarm-issue.md

Call it with /swarm-issue. For all projects use ~/.claude/commands/

Questions about swarm-issue

How do I install swarm-issue in Claude Code?

Add the command file at .claude/commands/swarm-issue.md.

What does swarm-issue do?

It prepares GitHub Issues for swarm work by analyzing tasks, suggesting agents, creating subtasks, and updating progress in GitHub.

What does swarm-issue need to work with GitHub Issues?

The examples use gh to read and edit issues and npx ruv-swarm to run swarm operations. GitHub steps require a configured gh installation.

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set76

The whole set →
architecture architecture designs system structure from specifications and pseudocode, covering components, interfaces, technology choices, and deployment. CX Codex ★ 850repo stars repo-architect repo-architect optimizes repository layouts and synchronizes files across projects using agent swarms. Helpful when setting up standard templates and multi-repo workflows. CX Codex +1 ★ 850repo stars swarm-pr swarm-pr coordinates agents working on a GitHub pull request, from diff analysis and review to reporting results back to the PR. CX Codex ★ 850repo stars code-review-swarm code-review-swarm sends a pull request through several review agents at once: security, performance, style, architecture. Handy when a plain diff and a linter no longer catch the trouble. CX Codex +1 ★ 850repo stars project-board-sync project-board-sync keeps a GitHub Projects board in step with a claude-flow agent swarm: cards, statuses, sprint metrics. Useful when several agents touch one repo. CX Codex ★ 850repo stars release-manager release-manager coordinates release pipelines using an agent swarm. It synchronizes versions across packages, executes tests, and opens a GitHub pull request. CX Codex +1 ★ 850repo stars adaptive-learner adaptive-learner — a subagent that pulls similar past cases from ReasoningBank before it starts and files the outcome afterwards, so later runs lean on what already happened. CX Codex ★ 850repo stars pagerank-analyzer The pagerank-analyzer subagent computes PageRank and examines graph structure. Use it to find influential nodes or assess connections across a network. CX Codex ★ 850repo stars

Project sponsors

Companies that keep this analytics open