run-github-project

Automates GitHub Project queue execution from triage through merge and reconciliation.

1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/citytexi/team-yg-pesonal-agent --skill run-github-project-citytexi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-github-project
Source: https://github.com/citytexi/team-yg-pesonal-agent/tree/main/.claude/skills/run-github-project
Command: npx skills add https://github.com/citytexi/team-yg-pesonal-agent --skill run-github-project-citytexi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Managing a GitHub Project board manually—triaging backlog items, planning issues, implementing tickets, shepherding PRs through review and CI, and reconciling merges—requires constant human coordination. This Skill treats the GitHub Project as a live control plane and autonomously drains authorized work through the full lifecycle. ## Core Features & Use Cases - Three operating modes: setup validates or repairs the repository's Project configuration, next executes one authorized issue end-to-end, and drain continuously processes eligible work until the queue is empty, blocked, or waiting on humans. - Authority-gated execution: Requires the ready-for-agent label, a human-authorized Planning transition, and explicit merge/issue-close authority before claiming or mutating any work. - Parallel ticket agents with a controller lane: Runs independent implementation slots concurrently with dedicated worktrees and persistent ticket agents, while serializing claims, merges, and Project mutations in one controller lane. - Failure isolation and recovery: Parks tickets with terminal required-CI failures using verifiable marker comments, reconstructs claims after restarts, and never loses state to ambiguous GitHub mutations. - Use Case: Point it at a repository whose GitHub Project has approved backlog items; it plans each issue, implements it with TDD, passes review gates, opens PRs, merges them, and reconciles the board—returning waiting-for-human only when human actions are all that remain. ## Quick Start Ask the agent to run the GitHub Project in next mode to plan, implement, and merge the highest-priority authorized issue on the board.

Frequently Asked Questions about run-github-project

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

FAQPage Schema
How do I automate a GitHub Project board with an AI agent?▼

Configure the repository's Project binding in docs/agents/run-github-project.md, then invoke the skill in next or drain mode. It claims authorized Ready-to-implement issues, implements them in dedicated worktrees, opens PRs, merges, and reconciles Project state automatically.

What is the difference between setup, next, and drain modes?▼

Setup only validates or repairs the Project configuration without running work. Next processes at most one selected issue end-to-end. Drain continuously executes all eligible authorized issues until the queue is empty, blocked, or only human actions remain.

What permissions does the skill need before executing GitHub Project work?▼

It requires the ready-for-agent label, a non-automated Planning transition by a configured execution approver, explicit merge authority for the mode's scope, and explicit issue-close authority when close-after-merge is configured. Standing authority expires on any stop or interruption.

Can the skill run multiple GitHub issues in parallel?▼

Yes, in drain mode it defaults to two concurrent implementation slots, each with its own ticket agent, worktree, branch, and PR. A conflict admission gate delays candidates with declared dependencies, shared resources, or overlapping plan paths.

What happens when required CI keeps failing on a pull request?▼

After three non-converging repair rounds with the same failure fingerprint, the claim is parked via a verified marker comment preserving the PR, branch, and assignment. It resumes only on a qualifying recovery signal such as a verified repair push or a materially new diagnostic direction.

Does the skill ever move human work or close epics automatically?▼

It never assigns or transitions human work; it only surfaces the human frontier packet. It closes a bare epic only after all native dependencies clear and explicit issue-close authority covers it, then refreshes the full Project graph.