
Agent Issue Tracker
Create, label, and coordinate GitHub issues with swarm-backed tracking when agents and humans share a delivery backlog.
Overview
agent-issue-tracker is an agent skill most often used in Build (also Ship, Operate) that orchestrates GitHub issue creation, labeling, and swarm-coordinated progress tracking.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-issue-trackerWhat is this skill?
- Automated issue creation with smart templates and intelligent labeling
- Progress tracking coordinated via Claude Flow swarm init, agent spawn, and task orchestrate MCP tools
- Multi-agent collaboration hooks for complex issues and milestone coordination
- Pre-hook requires GitHub CLI authentication before swarm issue setup
- Post-hook updates swarm memory with issue state after coordination completes
Adoption & trust: 649 installs on skills.sh; 58.5k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agents and you are shipping work in parallel but GitHub issues stay stale, unlabeled, and disconnected from swarm task state.
Who is it for?
Builders already using GitHub Issues plus Claude Flow MCP who want automated issue hygiene and multi-agent coordination on the same repo.
Skip if: Teams on Jira/Linear-only workflows without GitHub CLI, or anyone who cannot authenticate `gh` in the agent environment.
When should I use this skill?
Invoke with $agent-issue-tracker when you need intelligent issue management, swarm-coordinated updates, or cross-repo GitHub issue synchronization.
What do I get? / Deliverables
Issues are created from templates, orchestrated across agents, and reflected in swarm memory so progress monitoring matches the live backlog.
- Created or updated GitHub issues with templates and labels
- Initialized progress tracking and swarm memory issue state
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Issue tracking is where solo builders first formalize work during Build; this skill’s templates and orchestration anchor on project coordination even though it also supports ship and operate rhythms. Capabilities emphasize milestones, labeling, cross-repo sync, and task orchestration—classic PM/issue workflow on top of GitHub, not application code or infra deploys.
Where it fits
Spawn labeled issues from templates when an agent breaks a feature into trackable GitHub work items.
Open and orchestrate a launch checklist as linked issues before release day.
Sync cross-repository bugs and sync swarm memory after post-release triage.
How it compares
GitHub-native issue orchestration with swarm MCP hooks—not a standalone standalone project-management SaaS integration.
Common Questions / FAQ
Who is agent-issue-tracker for?
Solo and indie developers using Claude Code with Claude Flow MCP who treat GitHub Issues as the coordination layer between humans and spawned agents.
When should I use agent-issue-tracker?
In Build for backlog and milestone setup, during Ship when launch tasks need tracked issues, and in Operate when you synchronize progress and labels across repositories.
Is agent-issue-tracker safe to install?
It uses shell, GitHub CLI, and MCP tools that can create and modify issues; review the Security Audits panel on this page and restrict repo scope before enabling in production orgs.
SKILL.md
READMESKILL.md - Agent Issue Tracker
--- name: issue-tracker description: Intelligent issue management and project coordination with automated tracking, progress monitoring, and team coordination tools: mcp__claude-flow__swarm_init, mcp__claude-flow__agent_spawn, mcp__claude-flow__task_orchestrate, mcp__claude-flow__memory_usage, Bash, TodoWrite, Read, Write color: green type: development capabilities: - Automated issue creation with smart templates - Progress tracking with swarm coordination - Multi-agent collaboration on complex issues - Project milestone coordination - Cross-repository issue synchronization - Intelligent labeling and organization priority: medium hooks: pre: | echo "Starting issue-tracker..." echo "Initializing issue management swarm" gh auth status || (echo "GitHub CLI not authenticated" && exit 1) echo "Setting up issue coordination environment" post: | echo "Completed issue-tracker" echo "Issues created and coordinated" echo "Progress tracking initialized" echo "Swarm memory updated with issue state" --- # GitHub Issue Tracker ## Purpose Intelligent issue management and project coordination with ruv-swarm integration for automated tracking, progress monitoring, and team coordination. ## Capabilities - **Automated issue creation** with smart templates and labeling - **Progress tracking** with swarm-coordinated updates - **Multi-agent collaboration** on complex issues - **Project milestone coordination** with integrated workflows - **Cross-repository issue synchronization** for monorepo management ## Tools Available - `mcp__github__create_issue` - `mcp__github__list_issues` - `mcp__github__get_issue` - `mcp__github__update_issue` - `mcp__github__add_issue_comment` - `mcp__github__search_issues` - `mcp__claude-flow__*` (all swarm coordination tools) - `TodoWrite`, `TodoRead`, `Task`, `Bash`, `Read`, `Write` ## Usage Patterns ### 1. Create Coordinated Issue with Swarm Tracking ```javascript // Initialize issue management swarm mcp__claude-flow__swarm_init { topology: "star", maxAgents: 3 } mcp__claude-flow__agent_spawn { type: "coordinator", name: "Issue Coordinator" } mcp__claude-flow__agent_spawn { type: "researcher", name: "Requirements Analyst" } mcp__claude-flow__agent_spawn { type: "coder", name: "Implementation Planner" } // Create comprehensive issue mcp__github__create_issue { owner: "ruvnet", repo: "ruv-FANN", title: "Integration Review: claude-code-flow and ruv-swarm complete integration", body: `## 🔄 Integration Review ### Overview Comprehensive review and integration between packages. ### Objectives - [ ] Verify dependencies and imports - [ ] Ensure MCP tools integration - [ ] Check hook system integration - [ ] Validate memory systems alignment ### Swarm Coordination This issue will be managed by coordinated swarm agents for optimal progress tracking.`, labels: ["integration", "review", "enhancement"], assignees: ["ruvnet"] } // Set up automated tracking mcp__claude-flow__task_orchestrate { task: "Monitor and coordinate issue progress with automated updates", strategy: "adaptive", priority: "medium" } ``` ### 2. Automated Progress Updates ```javascript // Update issue with progress from swarm memory mcp__claude-flow__memory_usage { action: "retrieve", key: "issue/54$progress" } // Add coordinated progress comment mcp__github__add_issue_comment { owner: "ruvnet", repo: "ruv-FANN", issue_number: 54, body: `## 🚀 Progress Update ### Completed Tasks - ✅ Architecture review completed (agent-1751574161764) - ✅ Dependency analysis finished (agent-1751574162044) - ✅ Integration testing verified (agent-1751574162300) ### Current Status - 🔄 Documentation review in progress - 📊 Integration score: 89% (Excellent) ### Next Steps - Final validation and merge preparation --- 🤖 Generated