gh-project

Automate GitHub Project v2 issue status transitions and workpad comments.

16|2|Updated Mar 7, 2026

Search Tags:#automation #workflow #github #project-v2 #workpad #issue-status

Ready to run

npx skills add https://github.com/hojinzs/github-symphony --skill gh-project

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh-project
Source: https://github.com/hojinzs/github-symphony/tree/main/.codex/skills/gh-project
Command: npx skills add https://github.com/hojinzs/github-symphony --skill gh-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing GitHub Project v2 boards across multiple repositories can be error-prone and time-consuming when updating issue statuses and coordinating workpad actions.

Core Features & Use Cases

Status transitions: Move issues between project columns using predefined column IDs and option IDs.
Workpad integration: Add or update workpad comments to reflect plans, progress, and follow-up items.
Cross-repo automation: Apply consistent project governance across multiple repositories with deterministic commands.

Quick Start

Update a Project v2 item status and post a descriptive workpad comment using your repository's IDs.

Frequently Asked Questions about gh-project

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

FAQPage Schema

How do I automate GitHub Project v2 issue status transitions across multiple repositories?▼

Automate GitHub Project v2 issue status transitions by applying deterministic column and option ID mappings to move items. This Skill executes consistent cross-repo project governance using predefined local context files to manage board updates without manual intervention.

What is the best way to add workpad comments to GitHub Project v2 issues automatically?▼

Adding workpad comments to GitHub Project v2 issues is handled by posting descriptive follow-up notes reflecting plans and progress. The Skill integrates workpad updates directly into the automated workflow alongside status transitions for comprehensive issue tracking.

Do I need the gh CLI to manage GitHub Project v2 workflows automatically?▼

Yes, you need an authenticated gh CLI to execute GitHub Project v2 workflow actions. The Skill requires authenticated gh CLI access and a local context file containing your project, column, and option IDs to perform deterministic status transitions and workpad updates.

How does cross-repo project governance work with predefined column and option IDs?▼

Cross-repo project governance works by referencing predefined column and option IDs from a local context file to enforce deterministic transitions. This ensures consistent automated status management and workpad updates are applied uniformly across multiple repositories.

Why do GitHub Project v2 automated transitions require a local context file?▼

GitHub Project v2 automated transitions require a local context file because it stores the specific project, column, and option IDs needed for deterministic execution. This mapping ensures the Skill targets the correct board items when applying cross-repo status changes.