Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Agent skill for issue-tracker - invoke with $agent-issue-tracker
.claude/skills/agent-issue-tracker/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-10 | ✓→✓ | = Same ✓ | — | — |
| case-20 | ✗→✗ | = Same ✗ | — | — |
| case-03 | ✗→✗ | = Same ✗ | — | — |
| case-19 | ✗→✗ | = Same ✗ | — | — |
| case-01 | ✗→✗ | = Same ✗ | — | — |
Intelligent issue management and project coordination with ruv-swarm integration for automated tracking, progress monitoring, and team coordination.
mcp__github__create_issuemcp__github__list_issuesmcp__github__get_issuemcp__github__update_issuemcp__github__add_issue_commentmcp__github__search_issuesmcp__claude-flow__* (all swarm coordination tools)TodoWrite, TodoRead, Task, Bash, Read, Writejavascript// 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" }
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" } }
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 }
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" } }
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
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
$github pr-manager - Link issues to pull requests$github release-manager - Coordinate release issues$sparc orchestrator - Complex project coordination$sparc tester - Automated testing workflows| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-20 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 5 counted toward the lift figure. The other 17 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. A headline lift is not published for this run.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.