run-github-project

Operate a GitHub Project queue by claiming, planning, implementing, and merging issues.

1.0k|46|Updated May 12, 2026
One-click install
npx skills add https://github.com/chrisbanes/skills --skill run-github-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-github-project
Source: https://github.com/chrisbanes/skills/tree/main/skills/run-github-project
Command: npx skills add https://github.com/chrisbanes/skills --skill run-github-project

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Running a GitHub Project as a live work queue requires constant manual coordination: claiming issues, tracking status transitions, reconciling ambiguous remote mutations, and merging PRs safely. This Skill automates that controller workflow with strict authority, reconciliation, and preservation rules.

Core Features & Use Cases

  • Mode-based operation: Run in review, setup, next, or drain mode to inspect, configure, execute one issue, or continuously process the queue.
  • Planning and implementation lanes: Verify human-authorized Planning transitions, publish versioned implementation plans, and hand off Ready work to isolated ticket agents with dedicated worktrees.
  • Failure isolation and recovery: Reconcile unknown remote mutation outcomes, park terminal required-CI failures, and preserve blocked or human-owned work instead of losing it.
  • Use Case: Point the Skill at a repository with a configured GitHub Project, authorize drain mode, and it claims Ready issues, implements them via TDD with review gates, merges PRs, and reports the human frontier when only human actions remain.

Quick Start

Ask the assistant to run the GitHub Project workflow in setup mode to configure the repository binding, then use next mode to execute one authorized issue.

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 workflow with an AI agent?

Configure the repository binding with Project owner, field IDs, and role labels, then run the Skill in next or drain mode. It claims Ready issues, plans and implements them in isolated worktrees, and merges PRs under explicit authority.

What is the difference between next and drain mode?

Next mode processes at most one selected issue end to end. Drain mode runs multiple ticket agents concurrently across occupied slots and continues until the queue is empty, waiting on humans, or partially blocked.

Does this workflow require specific GitHub permissions?

Yes. It requires an authenticated GitHub identity with Project read/write access, the GitHub CLI project scope, and explicit merge authority before claiming execution work. Issue-close authority is required when close-after-merge is configured.

What happens when a remote GitHub mutation fails or times out?

The outcome is treated as unknown rather than failed. The Skill authoritatively reconciles the remote state before retrying or reporting success, preventing duplicate mutations or lost work.

Can it handle blocked or human-owned backlog items?

Yes. Blocked, dependency-gated, and human-owned items are preserved in their authoritative frontier or partial-drain report. Their state is never changed just to make the queue appear empty.