gh-stack-prs

Build and manage stacked GitHub pull requests using the gh stack CLI extension.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill gh-stack-prs-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-stack-prs
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/gh-stack-prs
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill gh-stack-prs-codercoco-studios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large changes shipped as one giant pull request are hard to review and slow to merge. This Skill automates decomposing a big change into a stack of small, dependent PRs using the gh stack CLI extension, handling branch chaining, incremental submission, rebasing after merges, and folding in review feedback. ## Core Features & Use Cases - Stack initialization and growth: Create all group branches at once with gh stack init, or add them incrementally with gh stack add as each group's scope becomes clear. - Incremental PR submission: Submit one group's PR at a time with gh stack submit --auto, then fix up titles and bodies to match Conventional Commit and Closes #N conventions via gh pr edit. - Sync and cleanup: After earlier PRs merge, gh stack sync --prune cascade-rebases remaining branches, force-pushes safely with --force-with-lease --atomic, and prunes merged branches. - Use Case: You are implementing a multi-phase Pulumi infrastructure migration touching dozens of files. Split it into ordered groups (pulumi-1-..., pulumi-2-...), submit each as its own reviewable PR, and re-sync the stack automatically as each one merges. ## Quick Start Ask the AI to decompose the current large change into a stack of small dependent PRs using gh stack, starting with gh stack init for the first group branch.

Frequently Asked Questions about gh-stack-prs

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

FAQPage Schema
How do I split a large pull request into stacked PRs on GitHub?

Use the gh stack CLI extension: run gh stack init with your ordered group branch names to create each branch based on the previous one, commit each group's changes, then run gh stack submit --auto to push branches and create PRs incrementally.

How do I rebase stacked PRs after the first one merges?

Run gh stack sync --prune after each merge. It fetches, fast-forwards main, cascade-rebases every remaining stack branch onto its updated parent, pushes atomically with --force-with-lease, and deletes local branches whose PRs already merged.

Can I use gh stack with multiple git worktrees?

No. gh stack sync and modify check out each sibling branch in turn, and git refuses to check out a branch already checked out in another worktree. Use one worktree for the entire stack and switch branches with gh stack checkout or gh stack add.

Why does gh stack add fail with nothing to commit?

gh stack add requires staged changes or an explicit staging flag. Pass -A to stage all changes or -u for tracked files only, together with -m for the commit message; otherwise the command fails instead of creating an empty branch.

When should I not use stacked pull requests?

Skip stacking for small, self-contained changes like a typical bug fix or one-file change, which work fine as a single PR. Also note gh stack modify is interactive-only, so structural stack restructuring needs a human at the terminal.