github-project-management

Use the triage command to analyze unlabeled issues, suggest labels based on keyword rules, and assign priority. The swarm analyzes issue content and maps it to label rules defined in a configuration file, then applies labels and assigns appropriate agent types.

Run board-init with your project ID and bidirectional sync mode, then define a status mapping in a board-sync YAML file. Swarm task states like pending, in_progress, and completed are automatically mapped to board columns such as Backlog, In Progress, and Done.

You need the GitHub CLI (gh) installed and authenticated, a ruv-swarm or claude-flow MCP server configured, and appropriate repository access permissions. The Skill also uses MCP tools for GitHub and claude-flow plus Bash, Read, Write, and TodoWrite.

Yes, the issue-to-swarm command fetches issue data, auto-decomposes it into subtasks, and assigns agents. You can also batch-process all issues labeled swarm-ready and update each issue with a subtask checklist and progress comments.

The Skill finds issues inactive for 30 days, analyzes each with a swarm to suggest close, keep, or needs-info actions, and labels them accordingly. Issues stale for 37 or more days are automatically closed with an explanatory comment.

Sync failures usually stem from permission issues, misconfigured webhooks, or rate limits. Run the board-diagnose command to check permissions, webhooks, and rate limits, test the sync, and surface any conflicts.