Agent Swarm Issue

作者 ruvnet6051f6702b61無授權條款74K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

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

僅含說明AI & Agents Productivity & Workflow

AI 產生的概覽

圍繞 GitHub issue 協調多代理集群，將 issue 拆解為任務並追蹤進度。

功能: 此技能會把 GitHub issue 轉換成多代理集群任務。它說明了分析 issue 內容、將 issue 拆解為子任務、指派代理、更新 issue 檢查清單與標籤，以及張貼進度留言的工作流程。內容也涵蓋分類、重複偵測、陳舊 issue 處理、里程碑與跨儲存庫協調，以及集群指標報告。
適用情境: 當你想圍繞 GitHub issue 以多個協同代理組織工作時使用，例如把大型 issue 拆成子任務、指派專用代理，或在 issue 上追蹤解決進度。它也適合分類、重複偵測與陳舊 issue 清理流程。
執行需求: 需要 GitHub 存取權（gh CLI 或 GitHub MCP 工具），以及指令中引用的 ruv-swarm / claude-flow 工具，包括集群初始化、代理產生、任務編排與記憶工具。此技能不附帶指令碼，僅為說明文件。

name: swarm-issue description: GitHub issue-based swarm coordination agent that transforms issues into intelligent multi-agent tasks with automatic decomposition and progress tracking type: coordination color: "#FF6B35" tools:

mcp__github__get_issue
mcp__github__create_issue
mcp__github__update_issue
mcp__github__list_issues
mcp__github__create_issue_comment
mcp__claude-flow__swarm_init
mcp__claude-flow__agent_spawn
mcp__claude-flow__task_orchestrate
mcp__claude-flow__memory_usage
TodoWrite
TodoRead
Bash
Grep
Read
Write hooks: pre:
- "Initialize swarm coordination system for GitHub issue management"
- "Analyze issue context and determine optimal swarm topology"
- "Store issue metadata in swarm memory for cross-agent access" post:
- "Update issue with swarm progress and agent assignments"
- "Create follow-up tasks based on swarm analysis results"
- "Generate comprehensive swarm coordination report"

Swarm Issue - Issue-Based Swarm Coordination

Overview

Transform GitHub Issues into intelligent swarm tasks, enabling automatic task decomposition and agent coordination with advanced multi-agent orchestration.

Core Features

1. Issue-to-Swarm Conversion

bash

# Create swarm from issue using gh CLI# Get issue detailsISSUE_DATA=$(gh issue view 456 --json title,body,labels,assignees,comments)
# Create swarm from issuenpx ruv-swarm github issue-to-swarm 456 \  --issue-data "$ISSUE_DATA" \  --auto-decompose \  --assign-agents
# Batch process multiple issuesISSUES=$(gh issue list --label "swarm-ready" --json number,title,body,labels)npx ruv-swarm github issues-batch \  --issues "$ISSUES" \  --parallel
# Update issues with swarm statusecho "$ISSUES" | jq -r '.[].number' | while read -r num; do  gh issue edit $num --add-label "swarm-processing"done

# Create swarm from issue using gh CLI# Get issue detailsISSUE_DATA=$(gh issue view 456 --json title,body,labels,assignees,comments)
# Create swarm from issuenpx ruv-swarm github issue-to-swarm 456 \  --issue-data "$ISSUE_DATA" \  --auto-decompose \  --assign-agents
# Batch process multiple issuesISSUES=$(gh issue list --label "swarm-ready" --json number,title,body,labels)npx ruv-swarm github issues-batch \  --issues "$ISSUES" \  --parallel
# Update issues with swarm statusecho "$ISSUES" | jq -r '.[].number' | while read -r num; do  gh issue edit $num --add-label "swarm-processing"done

2. Issue Comment Commands

Execute swarm operations via issue comments:

markdown

<!-- In issue comment -->$swarm analyze$swarm decompose 5$swarm assign @agent-coder$swarm estimate$swarm start

<!-- In issue comment -->$swarm analyze$swarm decompose 5$swarm assign @agent-coder$swarm estimate$swarm start

3. Issue Templates for Swarms

markdown

<!-- .github/ISSUE_TEMPLATE$swarm-task.yml -->name: Swarm Taskdescription: Create a task for AI swarm processingbody:  - type: dropdown    id: topology    attributes:      label: Swarm Topology      options:        - mesh        - hierarchical        - ring        - star  - type: input    id: agents    attributes:      label: Required Agents      placeholder: "coder, tester, analyst"  - type: textarea    id: tasks    attributes:      label: Task Breakdown      placeholder: |        1. Task one description        2. Task two description

<!-- .github/ISSUE_TEMPLATE$swarm-task.yml -->name: Swarm Taskdescription: Create a task for AI swarm processingbody:  - type: dropdown    id: topology    attributes:      label: Swarm Topology      options:        - mesh        - hierarchical        - ring        - star  - type: input    id: agents    attributes:      label: Required Agents      placeholder: "coder, tester, analyst"  - type: textarea    id: tasks    attributes:      label: Task Breakdown      placeholder: |        1. Task one description        2. Task two description

Issue Label Automation

Auto-Label Based on Content

javascript

// .github$swarm-labels.json{  "rules": [    {      "keywords": ["bug", "error", "broken"],      "labels": ["bug", "swarm-debugger"],      "agents": ["debugger", "tester"]    },    {      "keywords": ["feature", "implement", "add"],      "labels": ["enhancement", "swarm-feature"],      "agents": ["architect", "coder", "tester"]    },    {      "keywords": ["slow", "performance", "optimize"],      "labels": ["performance", "swarm-optimizer"],      "agents": ["analyst", "optimizer"]    }  ]}

// .github$swarm-labels.json{  "rules": [    {      "keywords": ["bug", "error", "broken"],      "labels": ["bug", "swarm-debugger"],      "agents": ["debugger", "tester"]    },    {      "keywords": ["feature", "implement", "add"],      "labels": ["enhancement", "swarm-feature"],      "agents": ["architect", "coder", "tester"]    },    {      "keywords": ["slow", "performance", "optimize"],      "labels": ["performance", "swarm-optimizer"],      "agents": ["analyst", "optimizer"]    }  ]}

Dynamic Agent Assignment

bash

# Assign agents based on issue contentnpx ruv-swarm github issue-analyze 456 \  --suggest-agents \  --estimate-complexity \  --create-subtasks

# Assign agents based on issue contentnpx ruv-swarm github issue-analyze 456 \  --suggest-agents \  --estimate-complexity \  --create-subtasks

Issue Swarm Commands

Initialize from Issue

bash

# Create swarm with full issue context using gh CLI# Get complete issue dataISSUE=$(gh issue view 456 --json title,body,labels,assignees,comments,projectItems)
# Get referenced issues and PRsREFERENCES=$(gh issue view 456 --json body --jq '.body' | \  grep -oE '#[0-9]+' | while read -r ref; do    NUM=${ref#\#}    gh issue view $NUM --json number,title,state 2>$dev$null || \    gh pr view $NUM --json number,title,state 2>$dev$null  done | jq -s '.')
# Initialize swarmnpx ruv-swarm github issue-init 456 \  --issue-data "$ISSUE" \  --references "$REFERENCES" \  --load-comments \  --analyze-references \  --auto-topology
# Add swarm initialization commentgh issue comment 456 --body "🐝 Swarm initialized for this issue"

# Create swarm with full issue context using gh CLI# Get complete issue dataISSUE=$(gh issue view 456 --json title,body,labels,assignees,comments,projectItems)
# Get referenced issues and PRsREFERENCES=$(gh issue view 456 --json body --jq '.body' | \  grep -oE '#[0-9]+' | while read -r ref; do    NUM=${ref#\#}    gh issue view $NUM --json number,title,state 2>$dev$null || \    gh pr view $NUM --json number,title,state 2>$dev$null  done | jq -s '.')
# Initialize swarmnpx ruv-swarm github issue-init 456 \  --issue-data "$ISSUE" \  --references "$REFERENCES" \  --load-comments \  --analyze-references \  --auto-topology
# Add swarm initialization commentgh issue comment 456 --body "🐝 Swarm initialized for this issue"

Task Decomposition

bash

# Break down issue into subtasks with gh CLI# Get issue bodyISSUE_BODY=$(gh issue view 456 --json body --jq '.body')
# Decompose into subtasksSUBTASKS=$(npx ruv-swarm github issue-decompose 456 \  --body "$ISSUE_BODY" \  --max-subtasks 10 \  --assign-priorities)
# Update issue with checklistCHECKLIST=$(echo "$SUBTASKS" | jq -r '.tasks[] | "- [ ] " + .description')UPDATED_BODY="$ISSUE_BODY
## Subtasks$CHECKLIST"
gh issue edit 456 --body "$UPDATED_BODY"
# Create linked issues for major subtasksecho "$SUBTASKS" | jq -r '.tasks[] | select(.priority == "high")' | while read -r task; do  TITLE=$(echo "$task" | jq -r '.title')  BODY=$(echo "$task" | jq -r '.description')    gh issue create \    --title "$TITLE" \    --body "$BODY
Parent issue: #456" \    --label "subtask"done

# Break down issue into subtasks with gh CLI# Get issue bodyISSUE_BODY=$(gh issue view 456 --json body --jq '.body')
# Decompose into subtasksSUBTASKS=$(npx ruv-swarm github issue-decompose 456 \  --body "$ISSUE_BODY" \  --max-subtasks 10 \  --assign-priorities)
# Update issue with checklistCHECKLIST=$(echo "$SUBTASKS" | jq -r '.tasks[] | "- [ ] " + .description')UPDATED_BODY="$ISSUE_BODY
## Subtasks$CHECKLIST"
gh issue edit 456 --body "$UPDATED_BODY"
# Create linked issues for major subtasksecho "$SUBTASKS" | jq -r '.tasks[] | select(.priority == "high")' | while read -r task; do  TITLE=$(echo "$task" | jq -r '.title')  BODY=$(echo "$task" | jq -r '.description')    gh issue create \    --title "$TITLE" \    --body "$BODY
Parent issue: #456" \    --label "subtask"done

Progress Tracking

bash

# Update issue with swarm progress using gh CLI# Get current issue stateCURRENT=$(gh issue view 456 --json body,labels)
# Get swarm progressPROGRESS=$(npx ruv-swarm github issue-progress 456)
# Update checklist in issue bodyUPDATED_BODY=$(echo "$CURRENT" | jq -r '.body' | \  npx ruv-swarm github update-checklist --progress "$PROGRESS")
# Edit issue with updated bodygh issue edit 456 --body "$UPDATED_BODY"
# Post progress summary as commentSUMMARY=$(echo "$PROGRESS" | jq -r '"## 📊 Progress Update
**Completion**: \(.completion)%**ETA**: \(.eta)
### Completed Tasks\(.completed | map("- ✅ " + .) | join("\n"))
### In Progress\(.in_progress | map("- 🔄 " + .) | join("\n"))
### Remaining\(.remaining | map("- ⏳ " + .) | join("\n"))
---🤖 Automated update by swarm agent"')
gh issue comment 456 --body "$SUMMARY"
# Update labels based on progressif [[ $(echo "$PROGRESS" | jq -r '.completion') -eq 100 ]]; then  gh issue edit 456 --add-label "ready-for-review" --remove-label "in-progress"fi

# Update issue with swarm progress using gh CLI# Get current issue stateCURRENT=$(gh issue view 456 --json body,labels)
# Get swarm progressPROGRESS=$(npx ruv-swarm github issue-progress 456)
# Update checklist in issue bodyUPDATED_BODY=$(echo "$CURRENT" | jq -r '.body' | \  npx ruv-swarm github update-checklist --progress "$PROGRESS")
# Edit issue with updated bodygh issue edit 456 --body "$UPDATED_BODY"
# Post progress summary as commentSUMMARY=$(echo "$PROGRESS" | jq -r '"## 📊 Progress Update
**Completion**: \(.completion)%**ETA**: \(.eta)
### Completed Tasks\(.completed | map("- ✅ " + .) | join("\n"))
### In Progress\(.in_progress | map("- 🔄 " + .) | join("\n"))
### Remaining\(.remaining | map("- ⏳ " + .) | join("\n"))
---🤖 Automated update by swarm agent"')
gh issue comment 456 --body "$SUMMARY"
# Update labels based on progressif [[ $(echo "$PROGRESS" | jq -r '.completion') -eq 100 ]]; then  gh issue edit 456 --add-label "ready-for-review" --remove-label "in-progress"fi

Advanced Features

1. Issue Dependencies

bash

# Handle issue dependenciesnpx ruv-swarm github issue-deps 456 \  --resolve-order \  --parallel-safe \  --update-blocking

# Handle issue dependenciesnpx ruv-swarm github issue-deps 456 \  --resolve-order \  --parallel-safe \  --update-blocking

2. Epic Management

bash

# Coordinate epic-level swarmsnpx ruv-swarm github epic-swarm \  --epic 123 \  --child-issues "456,457,458" \  --orchestrate

# Coordinate epic-level swarmsnpx ruv-swarm github epic-swarm \  --epic 123 \  --child-issues "456,457,458" \  --orchestrate

3. Issue Templates

bash

# Generate issue from swarm analysisnpx ruv-swarm github create-issues \  --from-analysis \  --template "bug-report" \  --auto-assign

# Generate issue from swarm analysisnpx ruv-swarm github create-issues \  --from-analysis \  --template "bug-report" \  --auto-assign

Workflow Integration

GitHub Actions for Issues

yaml

# .github$workflows$issue-swarm.ymlname: Issue Swarm Handleron:  issues:    types: [opened, labeled, commented]
jobs:  swarm-process:    runs-on: ubuntu-latest    steps:      - name: Process Issue        uses: ruvnet$swarm-action@v1        with:          command: |            if [[ "${{ github.event.label.name }}" == "swarm-ready" ]]; then              npx ruv-swarm github issue-init ${{ github.event.issue.number }}            fi

# .github$workflows$issue-swarm.ymlname: Issue Swarm Handleron:  issues:    types: [opened, labeled, commented]
jobs:  swarm-process:    runs-on: ubuntu-latest    steps:      - name: Process Issue        uses: ruvnet$swarm-action@v1        with:          command: |            if [[ "${{ github.event.label.name }}" == "swarm-ready" ]]; then              npx ruv-swarm github issue-init ${{ github.event.issue.number }}            fi

Issue Board Integration

bash

# Sync with project boardnpx ruv-swarm github issue-board-sync \  --project "Development" \  --column-mapping '{    "To Do": "pending",    "In Progress": "active",    "Done": "completed"  }'

# Sync with project boardnpx ruv-swarm github issue-board-sync \  --project "Development" \  --column-mapping '{    "To Do": "pending",    "In Progress": "active",    "Done": "completed"  }'

Issue Types & Strategies

Bug Reports

bash

# Specialized bug handlingnpx ruv-swarm github bug-swarm 456 \  --reproduce \  --isolate \  --fix \  --test

# Specialized bug handlingnpx ruv-swarm github bug-swarm 456 \  --reproduce \  --isolate \  --fix \  --test

Feature Requests

bash

# Feature implementation swarmnpx ruv-swarm github feature-swarm 456 \  --design \  --implement \  --document \  --demo

# Feature implementation swarmnpx ruv-swarm github feature-swarm 456 \  --design \  --implement \  --document \  --demo

Technical Debt

bash

# Refactoring swarmnpx ruv-swarm github debt-swarm 456 \  --analyze-impact \  --plan-migration \  --execute \  --validate

# Refactoring swarmnpx ruv-swarm github debt-swarm 456 \  --analyze-impact \  --plan-migration \  --execute \  --validate

Automation Examples

Auto-Close Stale Issues

bash

# Process stale issues with swarm using gh CLI# Find stale issuesSTALE_DATE=$(date -d '30 days ago' --iso-8601)STALE_ISSUES=$(gh issue list --state open --json number,title,updatedAt,labels \  --jq ".[] | select(.updatedAt < \"$STALE_DATE\")")
# Analyze each stale issueecho "$STALE_ISSUES" | jq -r '.number' | while read -r num; do  # Get full issue context  ISSUE=$(gh issue view $num --json title,body,comments,labels)    # Analyze with swarm  ACTION=$(npx ruv-swarm github analyze-stale \    --issue "$ISSUE" \    --suggest-action)    case "$ACTION" in    "close")      # Add stale label and warning comment      gh issue comment $num --body "This issue has been inactive for 30 days and will be closed in 7 days if there's no further activity."      gh issue edit $num --add-label "stale"      ;;    "keep")      # Remove stale label if present      gh issue edit $num --remove-label "stale" 2>$dev$null || true      ;;    "needs-info")      # Request more information      gh issue comment $num --body "This issue needs more information. Please provide additional context or it may be closed as stale."      gh issue edit $num --add-label "needs-info"      ;;  esacdone
# Close issues that have been stale for 37+ daysgh issue list --label stale --state open --json number,updatedAt \  --jq ".[] | select(.updatedAt < \"$(date -d '37 days ago' --iso-8601)\") | .number" | \  while read -r num; do    gh issue close $num --comment "Closing due to inactivity. Feel free to reopen if this is still relevant."  done

# Process stale issues with swarm using gh CLI# Find stale issuesSTALE_DATE=$(date -d '30 days ago' --iso-8601)STALE_ISSUES=$(gh issue list --state open --json number,title,updatedAt,labels \  --jq ".[] | select(.updatedAt < \"$STALE_DATE\")")
# Analyze each stale issueecho "$STALE_ISSUES" | jq -r '.number' | while read -r num; do  # Get full issue context  ISSUE=$(gh issue view $num --json title,body,comments,labels)    # Analyze with swarm  ACTION=$(npx ruv-swarm github analyze-stale \    --issue "$ISSUE" \    --suggest-action)    case "$ACTION" in    "close")      # Add stale label and warning comment      gh issue comment $num --body "This issue has been inactive for 30 days and will be closed in 7 days if there's no further activity."      gh issue edit $num --add-label "stale"      ;;    "keep")      # Remove stale label if present      gh issue edit $num --remove-label "stale" 2>$dev$null || true      ;;    "needs-info")      # Request more information      gh issue comment $num --body "This issue needs more information. Please provide additional context or it may be closed as stale."      gh issue edit $num --add-label "needs-info"      ;;  esacdone
# Close issues that have been stale for 37+ daysgh issue list --label stale --state open --json number,updatedAt \  --jq ".[] | select(.updatedAt < \"$(date -d '37 days ago' --iso-8601)\") | .number" | \  while read -r num; do    gh issue close $num --comment "Closing due to inactivity. Feel free to reopen if this is still relevant."  done

Issue Triage

bash

# Automated triage systemnpx ruv-swarm github triage \  --unlabeled \  --analyze-content \  --suggest-labels \  --assign-priority

# Automated triage systemnpx ruv-swarm github triage \  --unlabeled \  --analyze-content \  --suggest-labels \  --assign-priority

Duplicate Detection

bash

# Find duplicate issuesnpx ruv-swarm github find-duplicates \  --threshold 0.8 \  --link-related \  --close-duplicates

# Find duplicate issuesnpx ruv-swarm github find-duplicates \  --threshold 0.8 \  --link-related \  --close-duplicates

Integration Patterns

1. Issue-PR Linking

bash

# Link issues to PRs automaticallynpx ruv-swarm github link-pr \  --issue 456 \  --pr 789 \  --update-both

# Link issues to PRs automaticallynpx ruv-swarm github link-pr \  --issue 456 \  --pr 789 \  --update-both

2. Milestone Coordination

bash

# Coordinate milestone swarmsnpx ruv-swarm github milestone-swarm \  --milestone "v2.0" \  --parallel-issues \  --track-progress

# Coordinate milestone swarmsnpx ruv-swarm github milestone-swarm \  --milestone "v2.0" \  --parallel-issues \  --track-progress

3. Cross-Repo Issues

bash

# Handle issues across repositoriesnpx ruv-swarm github cross-repo \  --issue "org$repo#456" \  --related "org$other-repo#123" \  --coordinate

# Handle issues across repositoriesnpx ruv-swarm github cross-repo \  --issue "org$repo#456" \  --related "org$other-repo#123" \  --coordinate

Metrics & Analytics

Issue Resolution Time

bash

# Analyze swarm performancenpx ruv-swarm github issue-metrics \  --issue 456 \  --metrics "time-to-close,agent-efficiency,subtask-completion"

# Analyze swarm performancenpx ruv-swarm github issue-metrics \  --issue 456 \  --metrics "time-to-close,agent-efficiency,subtask-completion"

Swarm Effectiveness

bash

# Generate effectiveness reportnpx ruv-swarm github effectiveness \  --issues "closed:>2024-01-01" \  --compare "with-swarm,without-swarm"

# Generate effectiveness reportnpx ruv-swarm github effectiveness \  --issues "closed:>2024-01-01" \  --compare "with-swarm,without-swarm"

Best Practices

1. Issue Templates

Include swarm configuration options
Provide task breakdown structure
Set clear acceptance criteria
Include complexity estimates

2. Label Strategy

Use consistent swarm-related labels
Map labels to agent types
Priority indicators for swarm
Status tracking labels

3. Comment Etiquette

Clear command syntax
Progress updates in threads
Summary comments for decisions
Link to relevant PRs

Security & Permissions

Command Authorization: Validate user permissions before executing commands
Rate Limiting: Prevent spam and abuse of issue commands
Audit Logging: Track all swarm operations on issues
Data Privacy: Respect private repository settings

Examples

Complex Bug Investigation

bash

# Issue #789: Memory leak in productionnpx ruv-swarm github issue-init 789 \  --topology hierarchical \  --agents "debugger,analyst,tester,monitor" \  --priority critical \  --reproduce-steps

# Issue #789: Memory leak in productionnpx ruv-swarm github issue-init 789 \  --topology hierarchical \  --agents "debugger,analyst,tester,monitor" \  --priority critical \  --reproduce-steps

Feature Implementation

bash

# Issue #234: Add OAuth integrationnpx ruv-swarm github issue-init 234 \  --topology mesh \  --agents "architect,coder,security,tester" \  --create-design-doc \  --estimate-effort

# Issue #234: Add OAuth integrationnpx ruv-swarm github issue-init 234 \  --topology mesh \  --agents "architect,coder,security,tester" \  --create-design-doc \  --estimate-effort

Documentation Update

bash

# Issue #567: Update API documentationnpx ruv-swarm github issue-init 567 \  --topology ring \  --agents "researcher,writer,reviewer" \  --check-links \  --validate-examples

# Issue #567: Update API documentationnpx ruv-swarm github issue-init 567 \  --topology ring \  --agents "researcher,writer,reviewer" \  --check-links \  --validate-examples

Swarm Coordination Features

Multi-Agent Issue Processing

bash

# Initialize issue-specific swarm with optimal topologymcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 8 }mcp__claude-flow__agent_spawn { type: "coordinator", name: "Issue Coordinator" }mcp__claude-flow__agent_spawn { type: "analyst", name: "Issue Analyzer" }mcp__claude-flow__agent_spawn { type: "coder", name: "Solution Developer" }mcp__claude-flow__agent_spawn { type: "tester", name: "Validation Engineer" }
# Store issue context in swarm memorymcp__claude-flow__memory_usage {  action: "store",  key: "issue/#{issue_number}$context",  value: { title: "issue_title", labels: ["labels"], complexity: "high" }}
# Orchestrate issue resolution workflowmcp__claude-flow__task_orchestrate {  task: "Coordinate multi-agent issue resolution with progress tracking",  strategy: "adaptive",  priority: "high"}

# Initialize issue-specific swarm with optimal topologymcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 8 }mcp__claude-flow__agent_spawn { type: "coordinator", name: "Issue Coordinator" }mcp__claude-flow__agent_spawn { type: "analyst", name: "Issue Analyzer" }mcp__claude-flow__agent_spawn { type: "coder", name: "Solution Developer" }mcp__claude-flow__agent_spawn { type: "tester", name: "Validation Engineer" }
# Store issue context in swarm memorymcp__claude-flow__memory_usage {  action: "store",  key: "issue/#{issue_number}$context",  value: { title: "issue_title", labels: ["labels"], complexity: "high" }}
# Orchestrate issue resolution workflowmcp__claude-flow__task_orchestrate {  task: "Coordinate multi-agent issue resolution with progress tracking",  strategy: "adaptive",  priority: "high"}

Automated Swarm Hooks Integration

javascript

// Pre-hook: Issue Analysis and Swarm Setupconst preHook = async (issue) => {  // Initialize swarm with issue-specific topology  const topology = determineTopology(issue.complexity);  await mcp__claude_flow__swarm_init({ topology, maxAgents: 6 });    // Store issue context for swarm agents  await mcp__claude_flow__memory_usage({    action: "store",    key: `issue/${issue.number}$metadata`,    value: { issue, analysis: await analyzeIssue(issue) }  });};
// Post-hook: Progress Updates and Coordinationconst postHook = async (results) => {  // Update issue with swarm progress  await updateIssueProgress(results);    // Generate follow-up tasks  await createFollowupTasks(results.remainingWork);    // Store completion metrics  await mcp__claude_flow__memory_usage({    action: "store",     key: `issue/${issue.number}$completion`,    value: { metrics: results.metrics, timestamp: Date.now() }  });};

// Pre-hook: Issue Analysis and Swarm Setupconst preHook = async (issue) => {  // Initialize swarm with issue-specific topology  const topology = determineTopology(issue.complexity);  await mcp__claude_flow__swarm_init({ topology, maxAgents: 6 });    // Store issue context for swarm agents  await mcp__claude_flow__memory_usage({    action: "store",    key: `issue/${issue.number}$metadata`,    value: { issue, analysis: await analyzeIssue(issue) }  });};
// Post-hook: Progress Updates and Coordinationconst postHook = async (results) => {  // Update issue with swarm progress  await updateIssueProgress(results);    // Generate follow-up tasks  await createFollowupTasks(results.remainingWork);    // Store completion metrics  await mcp__claude_flow__memory_usage({    action: "store",     key: `issue/${issue.number}$completion`,    value: { metrics: results.metrics, timestamp: Date.now() }  });};

See also: swarm-pr.md [blocked], sync-coordinator.md [blocked], workflow-automation.md [blocked]

來源與署名

來源：ruvnet/ruflo位於.agents/skills/agent-swarm-issue提交6051f67

授權條款：無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

Agent Swarm Issue

Swarm Issue - Issue-Based Swarm Coordination

Overview

Core Features

1. Issue-to-Swarm Conversion

2. Issue Comment Commands

3. Issue Templates for Swarms

Issue Label Automation

Auto-Label Based on Content

Dynamic Agent Assignment

Issue Swarm Commands

Initialize from Issue

Task Decomposition

Progress Tracking

Advanced Features

1. Issue Dependencies

2. Epic Management

3. Issue Templates

Workflow Integration

GitHub Actions for Issues

Issue Board Integration

Issue Types & Strategies

Bug Reports

Feature Requests

Technical Debt

Automation Examples

Auto-Close Stale Issues

Issue Triage

Duplicate Detection

Integration Patterns

1. Issue-PR Linking

2. Milestone Coordination

3. Cross-Repo Issues

Metrics & Analytics

Issue Resolution Time

Swarm Effectiveness

Best Practices

1. Issue Templates

2. Label Strategy

3. Comment Etiquette

Security & Permissions

Examples

Complex Bug Investigation

Feature Implementation

Documentation Update

Swarm Coordination Features

Multi-Agent Issue Processing

Automated Swarm Hooks Integration

來源與署名

更多來自 ruvnet/ruflo 的技能

Cron Schedule

Autopilot Predict

Autopilot Loop

Worker Integration

Worker Benchmarks

Swarm Advanced

更多AI & Agents技能

Ppt Template Creator

Skill Development

Plugin Structure

Command Development

Claude Md Improver

Find Skills