glab-stack

Manage stacked merge requests in GitLab using the glab CLI.

43|5|Updated Jan 30, 2026

Search Tags:#development #code review #git workflow #gitlab #merge request #stacked diffs

One-click install

npx skills add https://github.com/vince-winkintel/gitlab-cli-skills --skill glab-stack

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: glab-stack
Source: https://github.com/vince-winkintel/gitlab-cli-skills/tree/main/glab-stack
Command: npx skills add https://github.com/vince-winkintel/gitlab-cli-skills --skill glab-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the management of complex, multi-part changes by enabling users to work with stacked merge requests, facilitating a more organized and efficient development workflow for dependent changes.

Core Features & Use Cases

Create Stacked Diffs: Initiate new stacked merge request workflows.
Navigate Stack: Move between the first, last, next, or previous diffs in a stack.
Sync Changes: Push local changes, rebase, and clean up merged/closed branches within the stack.
Use Case: When developing a new feature that requires several small, interdependent commits, use glab stack to manage these as a series of stacked MRs, ensuring each part is reviewed and integrated smoothly.

Quick Start

Use the glab stack skill to create a new stacked merge request for the feature 'cool-new-feature'.

Frequently Asked Questions about glab-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are stacked merge requests and when do I need them for GitLab?▼

Stacked merge requests break complex, multi-part changes into a series of dependent MRs. You need this workflow when developing features with interdependent commits, ensuring each part is reviewed and integrated smoothly before merging the next.

How do I create and manage stacked diffs in GitLab?▼

You can manage stacked diffs by creating a new stacked merge request workflow, navigating between the first, last, next, or previous diffs in the stack, and syncing changes by pushing local updates and rebasing branches.

How do I sync local changes and clean up branches in a stacked MR workflow?▼

To sync local changes in a stacked MR workflow, push your updates, rebase the dependent branches, and clean up any branches within the stack that have already been merged or closed.

Do I need the GitLab CLI installed to manage stacked merge requests?▼

Yes, managing stacked merge requests requires the GitLab CLI (`glab`) to be installed and configured in your environment before you can initiate, navigate, and sync dependent MRs.

What is the best way to handle dependent code reviews for a large feature?▼

The best way to handle dependent code reviews for a large feature is using stacked merge requests, which organize interdependent commits into a series of reviewable MRs rather than one massive pull request.