Skip to main content
command CX Codex

issue-tracker — Claude Code command: what it does, how to install

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

no license ★ 850 updated 2026-10-26

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

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

What it helps with

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

  • 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

How to install issue-tracker

Manually: put the files in place

.claude/commands/issue-tracker.md

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

Questions about issue-tracker

How to install issue-tracker in Claude Code?

Place the file at .claude/commands/issue-tracker.md.

What does issue-tracker do?

It coordinates GitHub issue creation, milestone updates, and progress monitoring using autonomous agent swarms.

What tools are required for issue-tracker to work?

You need configured GitHub and claude-flow MCP servers, plus the gh CLI for command-line batch actions.

Similar slash commands

All slash commands for Git and GitHub →
gh-issue-sync mitsuhiko gh-issue-sync — a skill for Claude Code, Codex, Cursor and other platforms that maps GitHub Issues to local Markdown files. The agent pulls, edits and pushes issues from inside the repo without touching the browser. CX Codex +1 28,500installs linear-task-to-issue davila7 linear-task-to-issue — a slash command that turns a Linear task into a GitHub issue, carrying over fields, links, attachments and comments. Useful when planning lives in Linear and code lives in GitHub. CX Codex +1 129installs resolve-issue sentimony resolve-issue — a skill for Claude Code and Codex that orchestrates a GitHub issue from intake through implementation and review. Runs upon providing an issue reference, supporting manual approvals or --auto mode. CX Codex +1 1,200installs github-project-management ruvnet github-project-management is a Claude Code skill for managing GitHub issues and coordinating agent swarms. It can triage issues, suggest labels, and turn requests into subtasks. CX Codex +1 1,400installs issue-progress-tracking OrchestKit issue-progress-tracking guides GitHub issue ceremonies using the gh CLI by updating progress labels, creating dedicated branches, enforcing atomic commits, and linking PRs. CX Codex +1 221installs issue-triage modelcontextprotocol issue-triage sorts incoming issues and PRs for the MCP servers repo. Moves valid tasks to the Servers V2 board and closes duplicates, spam, and misdirected requests with canned responses. CX Codex +1 ★ 92,149repo stars

From the same set76

The whole set →
commands The commands command for Claude Code is a reference for AI pair programming sessions, managing driver and navigator roles and running tests and code review from the terminal. CX Codex +1 ★ 850repo stars dual-orchestrator dual-orchestrator routes work between interactive Claude Code and headless Codex: use one for reasoning and review, the other for parallel execution. Built for workflows that combine both. CX Codex ★ 850repo stars pseudocode Turns a finished spec into pseudocode: algorithms, data structures and a complexity estimate before any code is written. CX Codex ★ 850repo stars tester tester — a subagent that designs and runs tests across the pyramid: units with mocks, integration against a real database, E2E flows, performance checks, and security validation. Keeps coverage above 80% and catches bugs early. CX Codex ★ 850repo stars goal-planner goal-planner — a GOAP planner subagent that turns a goal into an ordered set of actions and reworks the plan when a step fails. CX Codex ★ 850repo stars v3-memory-specialist The v3-memory-specialist subagent for Claude Code migrates scattered project memory into AgentDB with HNSW indexing, speeding semantic search and sharing context across agents. CX Codex ★ 850repo stars config Loads a reference for pair programming settings: driver, navigator and switch modes, verification thresholds, test runs and agent profiles kept in .claude-flow/pair-config.json. CX Codex +1 ★ 850repo stars workflow-automation workflow-automation integrates multi-agent swarms with GitHub Actions pipelines to generate CI configurations, select tests, and inspect build failures. CX Codex +1 ★ 850repo stars

Project sponsors

Companies that keep this analytics open