菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Define a semantic color system taxonomy and resolve bindings against a palette using get_color_system. Use when the user wants to map semantic token names (role, prominence, state…) to primitive color shades. Produces a SystemData object for use in semantic code generation or design tool deployment.
Entry point for UI Color Palette workflows targeting Figma. Use to choose between variables and styles generation.
Entry point for UI Color Palette workflows targeting Penpot. Use to choose between tokens, styles, and board/document preview generation.
Generate semantic code files alongside primitives by passing a color system configuration to generate_code. Use when the user wants design tokens or code that includes both primitive shades and semantic layer (role/prominence/state mappings). Requires a SystemConfiguration in context or gathered from the user.
Build a full color palette from source colors. Uses get_palette to generate scales and themes, then previews the result visually. Use when the user wants to create a complete palette before auditing, exporting, or deploying it.
Entry point for UI Color Palette workflows targeting Framer. Use to choose between color style synchronization and visual document preview generation.
| name | glab-stack |
| description | 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. |
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.
glab stack --help
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-base
Use --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.
See references/commands.md for full --help output.