Create and manage GitHub native stacked PRs with the gh stack CLI.
npx skills add https://github.com/PostHog/posthog-foss --skill stacking-prs
Please help me install this Agent Skill. Skill: stacking-prs Source: https://github.com/PostHog/posthog-foss/tree/main/.agents/skills/stacking-prs Command: npx skills add https://github.com/PostHog/posthog-foss --skill stacking-prs
Splitting a large change into reviewable pieces is painful when each PR depends on the previous one: rebases cascade, CI costs multiply, and merges can bypass required review paths. This Skill provides the operational workflow for creating, syncing, and landing GitHub native stacked PRs in the PostHog repo without breaking branch protections or the Trunk merge queue.
gh stack init, add layers with gh stack add, adopt existing branches or link existing PRs, and publish everything as draft PRs with gh stack submit --auto.gh stack sync, resolve rebase conflicts safely, handle force-with-lease refusals when bots push commits, and prune merged branches./trunk merge on the top PR or bottom-first through /merging-prs, never with gh stack merge.git push is blocked, build stacks with git_signed_commit and link them through the gh_stack MCP tool.Ask the agent to split your current branch into a stacked PR chain using gh stack and submit the layers as draft PRs.
High-intent search queries and answers about installing and using this skill.
Install the gh-stack extension with `gh extension install github/gh-stack`, then run `gh stack init` for the bottom branch and `gh stack add` for each layer above it. Publish the whole chain with `gh stack submit --auto`, which pushes branches and creates draft PRs with correct base branches.
Slice the change by reviewable unit, such as migration, backend, and frontend layers, keeping the stack shallow at two to four layers. Each layer must make sense to review and merge alone, with a conventional-commit title and a filled PR template.
No. In this repo `gh stack merge` is forbidden because it merges the chain through GitHub's API and bypasses the Trunk merge queue. Instead comment `/trunk merge` on the top PR after explicit user approval, or land layers bottom-first via the standard merge process.
Sync pushes with `--force-with-lease`, so it refuses when the remote branch moved, usually because a bot like ReviewHog pushed fix commits. Treat the refusal as a signal to fetch and read the new commits, never as a reason to force-push.
All branches must live in the same repository with no cross-fork stacks, and the chain must be strictly linear with no branching structures. Rule bypass and auto-merge are unsupported, GitHub Desktop has no stack support, and every layer needs its own approval and green checks.
maximhqSplit oversized commits into stacks of independently reviewable Graphite PRs.
bildzeitungAutomate code review and batch merging of approved branches into the trunk.
dtsongRequest GitHub pull request reviewers by analyzing changed files and CODEOWNERS.
dotnetManage stacked branches and dependent pull requests with the gh-stack GitHub CLI extension.