Agent skill · laurigates
git-stacked-prs
GitHub native stacked PRs via gh stack. Use when creating, syncing, rebasing or merging a PR stack, or choosing stacks vs manual PR chains.
What it needs
About 5k tokens when loaded.
What this skill does
GitHub Native Stacked PRs (gh stack) GitHub has a first-party stacked-PR model: a chain of PRs registered with GitHub, driven by the github/gh-stack CLI extension. A registered stack behaves differently from the ad-hoc chain this plugin's other skills describe — GitHub retargets, runs CI, and merges the stack itself. Public preview. The feature and its CLI surface are subject to change. No repository or organization setting enables it; it is on by default. When to Use This Skill Use this skill when... Use something else when... ------------------------ --------------------------- Building a change as a registered gh stack Rebasing a plain feature branch → git-rebase-patterns Deciding stack vs. ad-hoc PR chain Merging one PR safely → git-merge-hazards Merging or syncing a registered stack Creating a single PR → git-pr A repo's PRs show GitHub stack UI Cross-fork contribution → git-upstream-pr (stacks are same-repo only) Registered stack vs. ad-hoc chain Three hazards this plugin documents at length apply to ad-hoc chains (you opened PR B with --base pointing at PR A's branch). A stack registered with GitHub removes all three: Behaviour Ad-hoc chain Registered stack ----------- -------------- ------------------ Parent merges Child auto-closes if the parent's branch is deleted (git-merge-hazards §2) PRs above stay open and auto-retarget to the stack's base CI on pullrequest: branches: [main] Child gets no checks until retargeted (git-pr § Stacked PRs) Runs for every PR in the stack Rebasing after a parent lands Manual git rebase --onto <old-parent-tip> per child gh stack sync cascades it Required reviews, required status checks, and CODEOWNERS are enforced against the stack's base branch for every PR in the stack — a stack is not a way to route around branch protection. Ad-hoc chains remain the right tool where a stack cannot go: cross-fork work, and any repo where the merge tooling has not been updated (see Limits). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills laurigates/git-stacked-prs