Skills Agentes

Agent Issue Tracker

Gestión inteligente de issues y coordinación de proyectos, con seguimiento automatizado de progreso y colaboración entre equipos.

Estrellas
69.4k

en todo el repo

Actividad
27

0–100, la ruta de este skill

Actualizado
hace 6 meses

último commit aquí

Commits
0

últimos 90 días

Contexto
2.4k tok

16 tok en reposo

Paquete
1 archivo

9 KB

Instalar

Funciona con cualquier agente que lea SKILL.md

npx -y skills add ruvnet/ruflo --skill agent-issue-tracker --agent claude-code

Se instala solo en este repositorio.

Qué hace

  • Crea issues de GitHub con plantillas inteligentes y etiquetado automático
  • Rastrea el progreso con actualizaciones coordinadas por swarm de agentes
  • Coordina múltiples agentes en issues complejos (análisis de requisitos, planificación, testing)
  • Sincroniza issues entre repositorios en configuraciones monorepo

Úsalo cuando

  • Al crear un issue complejo que requiere seguimiento coordinado de progreso
  • Al necesitar sincronizar issues relacionados entre varios repositorios
  • Al gestionar hitos de proyecto con actualizaciones automáticas

No lo uses cuando

    Qué lo activa

    Di cualquiera de estas frases y el agente debería cargar este skill.

    • Crea un issue de integración con seguimiento de progreso automatizado
    • Busca issues abiertos con la etiqueta integration en este repo
    • Actualiza el progreso del issue 54 con los últimos avances

    SKILL.md

    En inglés

    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

    // 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

    // 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

    // 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:

    [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:

    ## 🔄 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:

    ## 🐛 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

    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

    Reproducido de ruvnet/ruflo bajo licencia MIT. Leer esta página en markdown.

    Archivos

    1 archivo en el paquete. Solo se lee SKILL.md al activarse — las referencias se cargan si el skill decide que las necesita.

    Antes de instalar

    Requiere GitHub CLI (gh) autenticado y las herramientas MCP mcp__github__* y mcp__claude-flow__*.

    Detalles

    Creador
    ruvnet
    Licencia
    MIT
    Recursos incluidos
    Solo SKILL.md
    Repositorio
    ruvnet/ruflo
    Código fuente
    Ver SKILL.md

    Etiquetas

    Más de ruvnet/ruflo

    Este repo incluye 275 skills. Si instalas uno, normalmente ya tienes los demás.

    Inspect and audit GEPA genomes via the `@metaharness/darwin/gepa` library entry (darwin 0.8.0) — load/validate a genome (default is the shipped cand-6 promotion), render the system prompt a genome compiles to, or classify failure modes in a run transcript. The `gepaOptimize` loop itself is library-only (bring your own evaluator) and not surfaced here — use `harness-evolve` for sandbox-scored evolution. Degrades gracefully when @metaharness/darwin is absent.

    Costo de contexto al activarse
    833 tok
    Tamaño del paquete
    1 archivo
    Última actualización
    hace 4 días
    Permisos
    herramientas desarrollo

    One-shot chat completion against DeepSeek's `deepseek-chat` model via the OpenAI-compatible /v1/chat/completions endpoint. Reads DEEPSEEK_API_KEY from the environment; degrades gracefully (exit 0 with a JSON status:degraded envelope) when the key is missing or the API is unreachable. Use for non-reasoning tasks — summarization, extraction, quick classification — where deepseek-reasoner would be overkill.

    Costo de contexto al activarse
    566 tok
    Tamaño del paquete
    1 archivo
    Última actualización
    hace 4 días
    Permisos
    herramientas desarrollo

    Reasoning-mode completion against DeepSeek's `deepseek-reasoner` model (R1) via /v1/chat/completions. Surfaces the model's chain-of-thought (`reasoning_content`) separately from the final answer (`content`), so callers can display or discard the CoT without re-parsing. Reads DEEPSEEK_API_KEY; degrades gracefully (exit 0 with status:degraded envelope) when unset or the API is unreachable. Ignores temperature/top_p per DeepSeek's spec for reasoner models.

    Costo de contexto al activarse
    627 tok
    Tamaño del paquete
    1 archivo
    Última actualización
    hace 4 días
    Permisos
    herramientas desarrollo

    Build or rebuild the ADR index + dependency graph by running scripts/import.mjs (handles v3-style and plugin-style ADR formats; one Bash call vs hundreds of MCP round-trips)

    Costo de contexto al activarse
    866 tok
    Tamaño del paquete
    1 archivo
    Última actualización
    hace 27 días
    herramientas desarrollo

    Create a new Architecture Decision Record with sequential numbering and AgentDB registration

    Costo de contexto al activarse
    680 tok
    Tamaño del paquete
    1 archivo
    Última actualización
    hace 27 días
    herramientas desarrollo

    Show AGNTCY/SLIM/CASA integration status — whether upstream AGNTCY packages are installed, which transport (local vs SLIM) is active, and whether CASA enforcement is enabled. Use when the user asks "is AGNTCY configured?", "show SLIM/CASA status", or "is AGNTCY/IOC integration active?".

    Costo de contexto al activarse
    443 tok
    Tamaño del paquete
    1 archivo
    Última actualización
    hace 26 días
    herramientas desarrollo