github-project

Automate GitHub Projects v2 workflows for issues, epics, and statuses.

18|4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/botminter/botminter --skill github-project-botminter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-project
Source: https://github.com/botminter/botminter/tree/main/profiles/scrum/coding-agent/skills/github-project
Command: npx skills add https://github.com/botminter/botminter --skill github-project-botminter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

GitHub Projects v2 requires careful coordination of issues, epics, stories, statuses, and workflow rules. This Skill automates setup, operation, and auditing of GitHub Project boards across teams, reducing manual drift and manual status syncing.

Core Features & Use Cases

  • Unified interface for board view, issue creation, status transitions, and attribution comments.
  • Create and manage native Epic/Task/Bug types; support for sub-issues (epic-to-story relationships) and milestones.
  • Automated verification of changes via GraphQL to ensure state changes actually took place.
  • Auto-recovery for missing project items or misconfigurations, with safe retry and audit logging.

Quick Start

Ask Claude to show the project board to begin managing your GitHub Projects v2 workflows.

Frequently Asked Questions about github-project

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

FAQPage Schema
How do I automate GitHub Projects v2 workflows for managing epics and stories?

You can automate GitHub Projects v2 workflows by using this Skill to create epics, stories, and bugs, transition statuses, assign people, and link PRs. It verifies changes with GraphQL queries and includes auto-recovery for missing items.

Can I manage sub-issues and epic-to-story relationships in GitHub Projects automatically?

Yes, managing sub-issues and epic-to-story relationships is supported automatically. The Skill creates and manages native Epic, Task, and Bug types while coordinating issue statuses across team project boards to reduce manual drift.

What's the best way to view a GitHub Project board and transition issue statuses via automation?

The best way to view a board and transition statuses is through the unified interface provided by this Skill. It automates status syncing, applies attribution comments, and verifies state changes via GraphQL to ensure transitions actually took place.

Do I need gh and jq installed to automate GitHub Projects v2 management?

Yes, you need both gh and jq installed as dependencies to automate GitHub Projects v2 management. The Skill relies on the GitHub CLI to execute workflows and jq to process JSON data for board setup and issue auditing.

Why does my automated GitHub Project status transition fail to reflect on the board?

Automated status transitions can fail due to missing project items or misconfigurations. This Skill addresses this by verifying state changes with GraphQL queries and providing auto-recovery with safe retries and audit logging for missing items.

Does this approach support linking pull requests and adding comments to GitHub issues?

Yes, linking pull requests and adding attribution comments to GitHub issues is fully supported. The Skill provides a unified interface for these tasks alongside board viewing, issue creation, and status management within GitHub Projects v2.