Skip to content
Back to skills

1 Issue To Swarm Conversion

ASecurity

Sub-skill of github-swarm-issue: 1. Issue-to-Swarm Conversion (+1).

  • 17 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 9, 2026
documentationgobashgit

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add vamseeachanta/workspace-hub --skill 1-issue-to-swarm-conversion --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 1 Issue To Swarm Conversion?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 1 Issue To Swarm Conversion
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vamseeachanta-1-issue-to-swarm-conversion/badge)](https://www.skillsdirectory.com/skills/vamseeachanta-1-issue-to-swarm-conversion)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: github-swarm-issue-1-issue-to-swarm-conversion
description: 'Sub-skill of github-swarm-issue: 1. Issue-to-Swarm Conversion (+1).'
version: 1.0.0
category: development
type: reference
scripts_exempt: true
---

# 1. Issue-to-Swarm Conversion (+1)

## 1. Issue-to-Swarm Conversion


```bash
# Get complete issue context
ISSUE=$(gh issue view 456 --json title,body,labels,assignees,comments,projectItems)

# Analyze issue complexity
BODY=$(echo "$ISSUE" | jq -r '.body')
LABEL_COUNT=$(echo "$ISSUE" | jq '.labels | length')
COMMENT_COUNT=$(echo "$ISSUE" | jq '.comments | length')

# Determine swarm topology based on complexity
if [ $LABEL_COUNT -gt 3 ] || [ ${#BODY} -gt 1000 ]; then
  TOPOLOGY="hierarchical"
  MAX_AGENTS=8
elif echo "$BODY" | grep -qE "(\[ \]|1\.|step)" ; then
  TOPOLOGY="mesh"
  MAX_AGENTS=5
else
  TOPOLOGY="ring"
  MAX_AGENTS=3
fi

echo "Issue #456: Using $TOPOLOGY topology with $MAX_AGENTS agents"

# Initialize swarm comment
gh issue comment 456 --body "## Swarm Initialized

**Topology**: $TOPOLOGY
**Agents**: $MAX_AGENTS

Processing issue for task decomposition..."
```


## 2. Task Decomposition


```bash
# Get issue body
ISSUE_BODY=$(gh issue view 456 --json body --jq '.body')

# Extract tasks from issue body (markdown checklist items)
TASKS=$(echo "$ISSUE_BODY" | grep -E '^\s*-\s*\[ \]' | sed 's/.*\[ \]//')

# Create subtask checklist
SUBTASK_LIST=""
TASK_NUM=1
echo "$TASKS" | while read -r task; do
  SUBTASK_LIST+="- [ ] $TASK_NUM. $task\n"
  TASK_NUM=$((TASK_NUM + 1))
done

# Update issue with structured subtasks
UPDATED_BODY="$ISSUE_BODY

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.