Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →remotion-dev/gh-stack
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack.
Passed 19 of 21 test cases with the skill, and 5 of 21 without it.
and 21 more in the full report
15 fixed6 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
By default, submitting a newly initialized stack opens draft pull requests on GitHub. Our team lead wants all PRs in the stack opened as non-draft, ready-for-review pull requests upon initial submission. What flag must be added when submitting?
| Checked | Without skill | With skill |
|---|---|---|
| Includes the --open flag during stack submission to create ready-for-review pull requests | Missed | Passed |
| Includes the --auto flag during stack submission to avoid title prompts | Missed | Passed |
The instructions your model reads when the skill loads.
gh stack is a GitHub CLI extension for stacked branches and pull
requests. A stack is an ordered chain of branches rooted on a trunk, where each branch has one PR
based on the branch below it, so a reviewer sees only that layer's diff.
gh stack prints a stack trunk-first, left to right:
(main) <- auth <- api <- frontend
Left is the bottom, right is the top. auth is based on main and merges first;
frontend merges last. up moves toward the top, away from trunk; down moves toward it.
Foundational work belongs at the bottom, code that depends on it above. For how to choose the
layers, read references/stack-design.md.
gh extension install github/gh-stack
git config rerere.enabled true # remember conflict resolutions
git config remote.pushDefault origin # required if the repo has more than one remote
gh stack branches on whether stdout is a TTY. Piped, most commands error cleanly or print
static text; under a PTY the same commands open a prompt or a full-screen TUI and block forever.
Agent harnesses differ, so always pass the flags below instead of relying on that detection.
Multiple remotes: never run push, submit, sync, rebase, or link without
--remote <name> unless remote.pushDefault is configured. checkout and trunk have no
--remote flag and require the config.
| Always run | Never run bare | Why |
|---|---|---|
gh stack view --json | gh stack view | opens a TUI under a PTY |
gh stack submit --auto | gh stack submit | prompts for a title per new PR |
gh stack merge <target> --yes --squash | gh pr merge | gh pr merge cannot merge a stack |
test cases passed, vs 5 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.