Files
Vince Lozada 09862709d9 Phase 1: Improve descriptions and add workflows (#12)
- Enhanced all skill descriptions with specific triggers and use cases
- Removed duplicate help output from top 5 skill bodies (mr, issue, ci, auth, repo)
- Added actionable workflow sections with real-world examples
- Improved root skill (gitlab-cli-skills) with better organization and common workflows
- Reduced token consumption by ~60-70% in updated skills
- Better alignment with OpenClaw progressive disclosure pattern

Addresses #11 Phase 1 objectives:
✅ All skill descriptions enhanced with triggers
✅ Duplicate content removed from SKILL.md files
✅ Workflows added to: glab-mr, glab-issue, glab-ci, glab-auth, glab-repo
✅ Root skill improved with navigation and common workflows

Skills now follow OpenClaw patterns:
- YAML frontmatter includes triggers
- Progressive disclosure (workflows in SKILL.md, details in references/)
- Concise, actionable content focused on procedural knowledge

Co-authored-by: Ubuntu <ubuntu@vps-9755df38.vps.ovh.us>
2026-02-11 22:47:01 -06:00

3.0 KiB

name, description
name description
glab-stack 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.

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 --help

Subcommands

See references/commands.md for full --help output.