glab-stack
Skill1 starsChanged 7 months agoMITView on GitHub
Manage stacked merge requests for complex multi-part changes. Use when creating dependent MRs, managing MR stacks, or working with multi-layer changes. Triggers on stack, stacked MRs, dependent MRs, MR stack, stacked changes.
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 68
Use --update-base when the base branch (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
glab stack
Overview
Stacked diffs are a way of creating small changes that build upon each other to ultimately deliver a feature. This
kind of workflow can be used to accelerate development time by continuing to build upon your changes, while earlier
changes in the stack are reviewed and updated based on feedback.
This feature is experimental. It might be broken or removed without any prior notice.
Read more about what experimental features mean at
https://docs.gitlab.com/policy/development_stages_support/
Use experimental features at your own risk.
USAGE
glab stack <command> [command] [--flags]
EXAMPLES
$ glab stack create cool-new-feature
$ glab stack sync
COMMANDS
amend [--flags] Save more changes to a stacked diff. (EXPERIMENTAL)
create Create a new stacked diff. (EXPERIMENTAL)
first Moves to the first diff in the stack. (EXPERIMENTAL)
last Moves to the last diff in the stack. (EXPERIMENTAL)
list Lists all entries in the stack. (EXPERIMENTAL)
move Moves to any selected entry in the stack. (EXPERIMENTAL)
next Moves to the next diff in the stack. (EXPERIMENTAL)
prev Moves to the previous diff in the stack. (EXPERIMENTAL)
reorder Reorder a stack of merge requests. (EXPERIMENTAL)
save [--flags] Save your progress within a stacked diff. (EXPERIMENTAL)
switch <stack-name> Switch between stacks. (EXPERIMENTAL)
sync Sync and submit progress on a stacked diff. (EXPERIMENTAL)
FLAGS
-h --help Show help for this command.
-R --repo Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.Quick start
glab stack --helpv1.89.0 Updates
v1.89.0+:
glab stack synchas a new--update-baseflag that rebases the stack onto the updated base branch before syncing.
# Sync stack and rebase onto updated base branch (v1.89.0+)
glab stack sync --update-baseUse --update-base when the base branch (e.g. main) has been updated and you want to rebase your entire stack on top of it before pushing.
Subcommands
See references/commands.md for full --help output.
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- cormacc/dotagents★ 138% same
Wrote their own version · 1
- vince-winkintel/gitlab-cli-skills★ 49same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository52 other files it gives its agents.
- gh-cliSkill
- glab-aliasSkill
- glab-apiSkill
- glab-attestationSkill
- glab-authSkill
- glab-changelogSkill
- glab-check-updateSkill
- glab-ciSkill
- glab-clusterSkill
- glab-completionSkill
- glab-configSkill
- glab-deploy-keySkill
- glab-duoSkill
- glab-gpg-keySkill
- glab-helpSkill
- glab-incidentSkill
- glab-issueSkill
- glab-iterationSkill
- glab-jobSkill
- glab-labelSkill
- glab-mcpSkill
- glab-milestoneSkill
- glab-mrSkill
- glab-opentofuSkill
- glab-quick-actionsSkill
- glab-releaseSkill
- glab-repoSkill
- glab-runner-controllerSkill
- glab-runnerSkill
- glab-scheduleSkill
- glab-securefileSkill
- glab-snippetSkill
- glab-ssh-keySkill
- glab-todoSkill
- glab-tokenSkill
- glab-userSkill
- glab-variableSkill
- glab-versionSkill
- glab-workitemsSkill
- gitlab-cli-skillsSkill
- ui-color-palette-audit-paletteSkill
- ui-color-palette-build-color-systemSkill
- ui-color-palette-figmaSkill
- ui-color-palette-framerSkill
- ui-color-palette-generate-codeSkill
- ui-color-palette-generate-semantic-codeSkill
- ui-color-palette-generate-source-colorsSkill
- ui-color-palette-helpSkill
- ui-color-palette-manage-palettesSkill
- ui-color-palette-penpotSkill
- ui-color-palette-scale-paletteSkill
- ui-color-palette-sketchSkill
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.

