rebase-stack
Skill10 starsChanged 21 days agoMITView on GitHub
Rebases a gh-stack-tracked chain of stacked branches onto its updated base, guides conflict resolution, validates the stack, and pushes every branch with fork-aware PR creation. Requires the gh-stack extension and an existing tracked multi-branch stack; refuses to run otherwise. Do NOT use it to rebase a single branch onto main — plain git rebase does that. Activated by commands: /start, /continue, /validate, /push.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-readySkill
- bugfixSkill
- code-reviewSkill
- cve-fixSkill
- designSkill
- docs-writerSkill
- e2eSkill
- implementSkill
- kcsSkill
- prdSkill
- sizingSkill
- skill-reviewerSkill
- gh-stackSkill
- report-bugSkill
- triageSkill
- ui-designSkill
- ui-implementSkill
- ux-designSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read skills/controller.md and follow it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Rebase Stack Workflow
Read skills/controller.md and follow it. It gates every phase, then routes:
| Command | Phase |
/start | commands/start.md — rebase the whole stack |
/continue | commands/continue.md — resume after a conflict |
/validate | commands/validate.md — test the trunk-adjacent branch, or every branch with --all |
/push | commands/push.md — push, then open missing PRs |
With no command, present the phases above and wait.
Refuses to run unless gh stack is installed and gh stack view --json exits
0. Neither has a fallback. See guidelines.md for scope and safety rules.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.