github_project_automation

Automates GitHub issue triage, project board synchronization, and sprint tracking using swarm coordination.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill github-project-automation-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github_project_automation
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/github_project_automation
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill github-project-automation-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing GitHub projects manually—triaging issues, updating project boards, tracking sprint progress, and closing stale issues—consumes significant team time and leads to inconsistent project state. This Skill automates the full GitHub project management lifecycle with swarm-coordinated agents. ## Core Features & Use Cases - Issue Management & Triage: Create, label, decompose, and auto-triage issues using the GitHub CLI and swarm agents, including stale issue detection and duplicate linking. - Project Board Automation: Initialize GitHub Projects boards, sync card status bidirectionally with swarm tasks, auto-assign cards, and build custom views and dashboards. - Sprint Planning & Analytics: Manage sprints and milestones, track velocity, burndown, cycle time, and generate KPI reports. - Use Case: A team lead creates a feature issue labeled 'swarm-ready'; the skill decomposes it into subtasks, adds it to the project board, assigns agents, and posts automated progress updates until completion. ## Quick Start Ask the agent to create a GitHub issue for a new feature, decompose it into subtasks, and add it to your project board with automated progress tracking.

Frequently Asked Questions about github_project_automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue triage and labeling?

Use the triage workflow with ruv-swarm to analyze unlabeled issues, suggest labels based on keyword rules, and assign priority. The skill supports auto-labeling rules defined in a JSON config mapping keywords like 'bug' or 'feature' to labels and agent types.

How to sync GitHub Projects board with automated task status?

Initialize the board with ruv-swarm board-init using your project ID, then run board-sync with a status mapping (e.g., pending to Backlog, in_progress to In Progress). It supports bidirectional sync, auto-moving cards, and real-time webhook updates.

Can I break down a GitHub issue into subtasks automatically?

Yes, the issue-decompose command analyzes an issue body and splits it into prioritized subtasks, updating the issue with a checklist. High-priority subtasks can be created as separate linked issues referencing the parent.

Does this work with the GitHub CLI and what permissions are needed?

Yes, all operations use the gh CLI and GitHub APIs, so you need an authenticated gh session with repo and project permissions. Board operations require access to GitHub Projects, and webhook-based real-time sync needs a reachable endpoint.

How are stale GitHub issues handled automatically?

The skill finds issues inactive for 30 days, analyzes each with a swarm agent, and either labels them stale with a warning comment, requests more info, or keeps them active. Issues stale beyond 37 days are closed automatically with an explanatory comment.

What are the limitations of swarm-based board synchronization?

Sync depends on GitHub API rate limits, correct field mapping configuration, and webhook availability for real-time updates. Conflicts require a defined resolution strategy such as source-wins, and large boards may need optimization like archiving completed cards.