# issue-tracker

issue-tracker coordinates GitHub issue tracking with multi-agent swarms to structure bug reports, run progress updates, and sync project tasks.

- 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/issue-tracker.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/issue-tracker

## What it does

This command combines GitHub issue workflows with multi-agent orchestration. It partitions workloads across specialized roles such as coordinators, researchers, and testers, generating structured issue templates for bug fixes and integration goals.

Under the hood, the workflow uses GitHub MCP functions like `mcp__github__create_issue` alongside `claude-flow` routines for agent topologies and shared memory. Batch operations also run via `gh` CLI commands directly in the terminal.

The command requires active MCP servers for GitHub and `claude-flow`. Without authorized MCP connections, swarm memory storage and direct issue commenting will fail.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

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

### Codex

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

### GitHub Copilot

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

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/issue-tracker.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/issue-tracker.md

## When to use it
- structure integration tasks and bug reports with standard templates
- assign issue investigation steps across coordinated sub-agents
- publish progress updates directly to GitHub issue comments
- coordinate multi-issue project tracking using shared memory

## Example prompts
- Run issue-tracker to create an integration ticket for package updates
- Spawn an issue management swarm to investigate a reproduction bug
- Fetch progress from swarm memory and post an update comment to issue 54

## Similar
- [gh-issue-sync](https://affpapa.org/en/nevibecode/skills/gh-issue-sync.md) — skill · 28500 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
- [github-project-management](https://affpapa.org/en/nevibecode/skills/github-project-management.md) — skill · 1400 installs
- [issue-progress-tracking](https://affpapa.org/en/nevibecode/skills/issue-progress-tracking.md) — skill · 221 installs
- [issue-triage](https://affpapa.org/en/nevibecode/skills/issue-triage.md) — skill · ★ 92149 repo stars

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
