Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/stack-rebase
Cascades a rebase through an entire PR stack after a base PR merges or upstream changes.
Passed 17 of 20 test cases with the skill, and 13 of 20 without it.
and 2 more in the full report
5 fixed14 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
A base PR in my stack just merged on GitHub. I'm about to determine whether the merged slice is in `origin/master` and start rebasing. What step must be executed before inspecting remote merge status or stack topology?
| Checked | Without skill | With skill |
|---|---|---|
| Runs git fetch origin before analyzing branch states. | Missed | Passed |
The instructions your model reads when the skill loads.
Cascade a rebase through an entire PR stack after a base PR merges or the upstream base branch changes.
Run stack-rebase in any of these situations:
master; the
second PR now needs to target master directlymaster has moved forward and stack branches need to
incorporate the new commitssanctum:stack-push)sanctum:stack-create)git branch --list)git fetch origin)git status)--update-refsCreate TodoWrite items before starting:
stack-rebase:fetch-completestack-rebase:trigger-identifiedstack-rebase:rebase-completestack-rebase:conflicts-resolvedstack-rebase:force-pushedstack-rebase:prs-updatedfetch-complete)test cases passed, vs 13 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.