Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/stack-push
Pushes all branches in a stack and opens or updates one dependent PR per slice. Use after stack-create to publish the stack or after adding commits to a slice.
Passed 18 of 21 test cases with the skill, and 10 of 21 without it.
and 7 more in the full report
10 fixed11 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
In a 4-slice stack `stack/billing-ui`, which pull request should receive the summary navigation comment?
| Checked | Without skill | With skill |
|---|---|---|
| Posts the stack navigation table specifically on the root pull request. | Missed | Passed |
The instructions your model reads when the skill loads.
Push all branches in a stack and open (or update) one PR per slice, with each PR targeting its parent branch as base.
Run stack-push after stack-create has initialized the
branch topology and at least one commit exists on each
slice branch.
Also run it after adding commits to any slice to update
open PRs.
sanctum:stack-create)sanctum:stack-rebase)stack-create completed: branches exist with commitsgh CLI authenticated (gh auth status)Create TodoWrite items before starting:
stack-push:branches-listedstack-push:branches-pushedstack-push:prs-openedstack-push:stack-summary-postedbranches-listed)Identify all branches in the stack.
By convention they share a stack/<feature-name>/ prefix:
test cases passed, vs 10 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.