Agent skill

Agent Issue Tracker

by ruvnet in ruvnet/ruflo

Agent skill for issue-tracker - invoke with $agent-issue-tracker

MITAuto-check passedDevelopment

Install Agent Issue Tracker

skills CLI
$ npx skills add ruvnet/ruflo --skill agent-issue-tracker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ruvnet/ruflo agent-issue-tracker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ruvnet/ruflo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/agent-issue-tracker .claude/skills/agent-issue-tracker && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-issue-tracker
GitHub stars
74k
Used in
3 other repos
Token cost
~2.4k tokens
SKILL.md length
352 words
Files
1
Skills in repo
264
Repo updated
First seen
Licence
MIT

At a glance

Agent skill for issue-tracker - invoke with $agent-issue-tracker

  • Works in 7 steps: Create Coordinated Issue with Swarm… → Automated Progress Updates → Multi-Issue Project Coordination → …
  • Tasks that involve Issue triage
  • SKILL.md covers Purpose, Capabilities, Tools Available and Usage Patterns, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Agent Issue Tracker is an agent skill from ruvnet/ruflo. Agent skill for issue-tracker - invoke with $agent-issue-tracker

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Issue triage. It works with GitHub and Model Context Protocol. The repository describes itself as: 🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory…. The licence is MIT.

When your agent uses it

  • Tasks that involve Issue triage

Example prompts

  • “/agent-issue-tracker”

Requirements

  • Node.js

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Create Coordinated Issue with Swarm Tracking
  2. Automated Progress Updates
  3. Multi-Issue Project Coordination
  4. Swarm-Coordinated Issue Management
  5. Automated Progress Tracking
  6. Smart Labeling and Organization
  7. Batch Issue Operations

What it can do on your machine

Read from SKILL.md and the folder at commit de590e1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Issue Tracker loads about 2.4k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 352 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~21
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ruvnet/ruflo at commit de590e1, republished under its MIT licence (© ruvnet). 352 words, ~2,360 tokens.

Download SKILL.mdSave it as .claude/skills/agent-issue-tracker/SKILL.md (or your agent's skills folder).
name
agent-issue-tracker
description
Agent skill for issue-tracker - invoke with $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 with Claude Code using ruv-swarm coordination`
}

// Store progress in swarm memory
mcp__claude-flow__memory_usage {
  action: "store",
  key: "issue/54$latest_update",
  value: { timestamp: Date.now(), progress: "89%", status: "near_completion" }
}
3. Multi-Issue Project Coordination
javascript
// Search and coordinate related issues
mcp__github__search_issues {
  q: "repo:ruvnet$ruv-FANN label:integration state:open",
  sort: "created",
  order: "desc"
}

// Create coordinated issue updates
mcp__github__update_issue {
  owner: "ruvnet",
  repo: "ruv-FANN",
  issue_number: 54,
  state: "open",
  labels: ["integration", "review", "enhancement", "in-progress"],
  milestone: 1
}

Batch Operations Example

Complete Issue Management Workflow:
javascript
[Single Message - Issue Lifecycle Management]:
  // Initialize issue coordination swarm
  mcp__claude-flow__swarm_init { topology: "mesh", maxAgents: 4 }
  mcp__claude-flow__agent_spawn { type: "coordinator", name: "Issue Manager" }
  mcp__claude-flow__agent_spawn { type: "analyst", name: "Progress Tracker" }
  mcp__claude-flow__agent_spawn { type: "researcher", name: "Context Gatherer" }
  
  // Create multiple related issues using gh CLI
  Bash(`gh issue create \
    --repo :owner/:repo \
    --title "Feature: Advanced GitHub Integration" \
    --body "Implement comprehensive GitHub workflow automation..." \
    --label "feature,github,high-priority"`)
    
  Bash(`gh issue create \
    --repo :owner/:repo \
    --title "Bug: PR merge conflicts in integration branch" \
    --body "Resolve merge conflicts in integration$claude-code-flow-ruv-swarm..." \
    --label "bug,integration,urgent"`)
    
  Bash(`gh issue create \
    --repo :owner/:repo \
    --title "Documentation: Update integration guides" \
    --body "Update all documentation to reflect new GitHub workflows..." \
    --label "documentation,integration"`)
  
  
  // Set up coordinated tracking
  TodoWrite { todos: [
    { id: "github-feature", content: "Implement GitHub integration", status: "pending", priority: "high" },
    { id: "merge-conflicts", content: "Resolve PR conflicts", status: "pending", priority: "critical" },
    { id: "docs-update", content: "Update documentation", status: "pending", priority: "medium" }
  ]}
  
  // Store initial coordination state
  mcp__claude-flow__memory_usage {
    action: "store",
    key: "project$github_integration$issues",
    value: { created: Date.now(), total_issues: 3, status: "initialized" }
  }

Smart Issue Templates

Integration Issue Template:
markdown
## 🔄 Integration Task

### Overview
[Brief description of integration requirements]

### Objectives
- [ ] Component A integration
- [ ] Component B validation  
- [ ] Testing and verification
- [ ] Documentation updates

### Integration Areas
#### Dependencies
- [ ] Package.json updates
- [ ] Version compatibility
- [ ] Import statements

#### Functionality  
- [ ] Core feature integration
- [ ] API compatibility
- [ ] Performance validation

#### Testing
- [ ] Unit tests
- [ ] Integration tests
- [ ] End-to-end validation

### Swarm Coordination
- **Coordinator**: Overall progress tracking
- **Analyst**: Technical validation
- **Tester**: Quality assurance
- **Documenter**: Documentation updates

### Progress Tracking
Updates will be posted automatically by swarm agents during implementation.

---
🤖 Generated with Claude Code
Bug Report Template:
markdown
## 🐛 Bug Report

### Problem Description
[Clear description of the issue]

### Expected Behavior
[What should happen]

### Actual Behavior  
[What actually happens]

### Reproduction Steps
1. [Step 1]
2. [Step 2]
3. [Step 3]

### Environment
- Package: [package name and version]
- Node.js: [version]
- OS: [operating system]

### Investigation Plan
- [ ] Root cause analysis
- [ ] Fix implementation
- [ ] Testing and validation
- [ ] Regression testing

### Swarm Assignment
- **Debugger**: Issue investigation
- **Coder**: Fix implementation
- **Tester**: Validation and testing

---
🤖 Generated with Claude Code

Best Practices

Show full SKILL.md (141 more words)Show less
1. Swarm-Coordinated Issue Management
  • Always initialize swarm for complex issues
  • Assign specialized agents based on issue type
  • Use memory for progress coordination
2. Automated Progress Tracking
  • Regular automated updates with swarm coordination
  • Progress metrics and completion tracking
  • Cross-issue dependency management
3. Smart Labeling and Organization
  • Consistent labeling strategy across repositories
  • Priority-based issue sorting and assignment
  • Milestone integration for project coordination
4. Batch Issue Operations
  • Create multiple related issues simultaneously
  • Bulk updates for project-wide changes
  • Coordinated cross-repository issue management

Integration with Other Modes

Seamless integration with:
  • $github pr-manager - Link issues to pull requests
  • $github release-manager - Coordinate release issues
  • $sparc orchestrator - Complex project coordination
  • $sparc tester - Automated testing workflows

Metrics and Analytics

Automatic tracking of:
  • Issue creation and resolution times
  • Agent productivity metrics
  • Project milestone progress
  • Cross-repository coordination efficiency
Reporting features:
  • Weekly progress summaries
  • Agent performance analytics
  • Project health metrics
  • Integration success rates

© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/agent-issue-tracker of ruvnet/ruflo.

Open the folder on GitHubat commit de590e1

Used in 3 other repositories

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in ruvnet/ruflo, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Agent Issue Tracker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Issue Tracker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Issue Tracker this skillruvnet/ruflo74k3 repos~2.4kAutomated safety check: PassMIT
Herdr Issue Triageherdrdev/herdr43k—~517Automated safety check: PassApache-2.0
Issue Triagemono/SkiaSharp5.6k—~3.4kAutomated safety check: PassMIT
Issue Triage Loopcobusgreyling/loop-engineering11k—~522Automated safety check: PassMIT
Triagearcee-ai/nac279—~2kAutomated safety check: PassApache-2.0
TMDb Backlog Triageradamayoung/TMDb178—~5kAutomated safety check: PassApache-2.0

Similar skills

  • Herdr Issue Triage

    herdrdev/herdr

    Triages open herdr GitHub issues into a short decision-first Markdown table with a priority light, recommendation, age, reactions and a reason for each.

    43k GitHub stars~517 tokensUpdated today
    DevelopmentAuto-check passed
  • Issue Triage

    mono/SkiaSharp

    Triage a SkiaSharp GitHub issue or PR into structured JSON with classification (type, area, platform, severity), suggested response, automatable actions, and companion Markdown/HTML reports.

    5.6k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Issue Triage Loop

    cobusgreyling/loop-engineering

    Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.

    11k GitHub stars~522 tokensUpdated today
    DevelopmentAuto-check passed
  • Triage

    arcee-ai/nac

    Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked…

    279 GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • TMDb Backlog Triager

    adamayoung/TMDb

    Grooms the Backlog column of a GitHub project board by re-verifying each issue against current main, closing dead ones, promoting actionable ones to Ready and naming the decision the rest need.

    178 GitHub stars~5k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • GitHub Issues

    Cybereason-Public/owLSM

    Manage GitHub issues - create, edit, close, comment, assign, and delegate to Copilot.

    280 GitHub stars~1.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from ruvnet/ruflo

All 264 skills in this repo
  • Stores, searches, and retrieves successful patterns with HNSW-indexed semantic search so agents can reuse past solutions instead of relearning them.

    74k GitHub starsUsed in 2 repos~830 tokens
    Auto-check passed
  • Runs claude-flow CLI security scans for input validation, path traversal, SQL injection, XSS, hardcoded secrets and known CVEs, and writes an audit report.

    74k GitHub starsUsed in 2 repos~823 tokens
    Auto-check passed
  • Applies the SPARC method (specification, pseudocode, architecture, refinement, completion) with 17 specialized modes and multi-agent orchestration, from research to deployment.

    74k GitHub starsUsed in 2 repos~829 tokens
    Auto-check passed
  • Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.

    74k GitHub starsUsed in 2 repos~779 tokens
    Auto-check passed
  • Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Auto-check passed
  • Agent Coordination

    ruvnet/ruflo

    Reference for spawning, listing, monitoring and stopping agents with claude-flow commands, with agent type families, routing codes and coordination tips.

    74k GitHub starsUsed in 2 repos~519 tokens
    Auto-check passed

Categories

Questions about Agent Issue Tracker

What does Agent Issue Tracker do?

Agent skill for issue-tracker - invoke with $agent-issue-tracker. Agent Issue Tracker is an agent skill from ruvnet/ruflo.

When should I use Agent Issue Tracker?

Agent Issue Tracker fits situations like: tasks that involve Issue triage.

How do I install Agent Issue Tracker in Claude Code?

Run `npx skills add ruvnet/ruflo --skill agent-issue-tracker -a claude-code`. Or copy the skill folder (.agents/skills/agent-issue-tracker in ruvnet/ruflo) into .claude/skills/agent-issue-tracker in your project. Claude Code loads it when a task matches its description.

How do I install Agent Issue Tracker in Codex?

Run `npx skills add ruvnet/ruflo --skill agent-issue-tracker -a codex`. Or copy the skill folder (.agents/skills/agent-issue-tracker in ruvnet/ruflo) into .agents/skills/agent-issue-tracker in your project. Codex loads it when a task matches its description.

Can I use Agent Issue Tracker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruvnet/ruflo --skill agent-issue-tracker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-issue-tracker, .gemini/skills/agent-issue-tracker, .github/skills/agent-issue-tracker and .opencode/skills/agent-issue-tracker in your project.

What does Agent Issue Tracker need to run?

SKILL.md names no scripts, command-line tools or credentials: Agent Issue Tracker is instructions for the agent only. Our summary lists: Node.js.

Does Agent Issue Tracker access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Issue Tracker safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agent Issue Tracker use?

Agent Issue Tracker is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Issue Tracker use?

About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Issue Tracker?

Skills that share tags, products or a category with Agent Issue Tracker: Herdr Issue Triage (herdrdev/herdr, 43k stars), Issue Triage (mono/SkiaSharp, 5.6k stars), Issue Triage Loop (cobusgreyling/loop-engineering, 11k stars) and Triage (arcee-ai/nac, 279 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Issue Tracker?

ruvnet (a GitHub user) maintains it in ruvnet/ruflo, which has 74,012 GitHub stars. The repository holds 264 skills in this directory. The repository was last updated on October 7, 2026.

Source: ruvnet/ruflo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.