gh-project-pr

Automate bulk PR review and merge workflows in GitHub Projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/wscffaa/claude-gh-skills --skill gh-project-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-project-pr
Source: https://github.com/wscffaa/claude-gh-skills/tree/main/gh-project-pr
Command: npx skills add https://github.com/wscffaa/claude-gh-skills --skill gh-project-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the end-to-end workflow of reviewing and merging PRs across GitHub Projects by mapping Issues to their related PRs, enabling proactive progress tracking and faster delivery.

Core Features & Use Cases

  • Map Issues to PRs across GitHub Projects and surface progress at a glance
  • Locate related PRs via linked:issue, branch name patterns, and body references
  • Batch review and auto-merge workflows with optional CI gating and status updates
  • Use Case: A team wants to move multiple open Issues into merged PRs with minimal manual steps while keeping the Project board in sync

Quick Start

Run a dry-run for a given project: python3 scripts/main.py --project 1 --dry-run

Frequently Asked Questions about gh-project-pr

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

FAQPage Schema
How do I automate bulk PR review and merge workflows in GitHub Projects?

Automate bulk PR review and merge workflows in GitHub Projects by mapping Issues to their related PRs. This Skill locates PRs via linked issues, branch patterns, and body references, then sorts by priority to perform batch reviews with optional auto-merge and CI gates.

How does mapping GitHub Project Issues to pull requests work?

Mapping GitHub Project Issues to pull requests works by discovering PRs through linked issue references, matching branch name patterns, and scanning PR body references. This mechanism surfaces related PR progress at a glance and keeps the Project board synchronized during batch merges.

Do I need GitHub CLI and Python to batch merge pull requests?

Yes, you need GitHub CLI and Python 3 to batch merge pull requests using this automation. These dependencies orchestrate project board updates, locate linked PRs, execute batch reviews, and enforce optional CI gating before performing any auto-merge actions.

Can I run a dry-run for batch PR reviews on a GitHub Project?

Yes, you can run a dry-run for batch PR reviews on a GitHub Project. Execute `python3 scripts/main.py --project 1 --dry-run` to preview discovered PRs, mapped issues, and priority sorting without performing actual review or merge actions.

What is the best way to keep a GitHub Project board in sync when merging multiple PRs?

The best way to keep a GitHub Project board in sync when merging multiple PRs is automating the end-to-end workflow. By mapping Issues to related PRs and applying batch auto-merge with CI gates, the Skill proactively updates project progress and minimizes manual steps.

How do CI gates work with automated PR merging?

CI gates work with automated PR merging by acting as optional checks before batch auto-merge execution. The Skill orchestrates PR actions through GitHub CLI, ensuring CI status updates are verified so only passing PRs are merged while keeping the Project board updated.