glab-cli

Manage GitLab merge requests, issues, and CI/CD operations via glab CLI.

7|2|Updated Feb 25, 2026

Search Tags:#ci/cd #issues #gitlab #merge requests #api calls #pipeline debugging #glab cli

One-click install

npx skills add https://github.com/wenerme/ai --skill glab-cli-wenerme

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you perform common GitLab tasks (merge requests, issues, and CI/CD operations) from the terminal without manually switching to the web UI.

Core Features & Use Cases

Merge Request workflows: Create, view, checkout, approve, merge, and manage MR lifecycle with recommended safety flags and pipeline-aware merging.
Issue management: Create, list, close, and update issues with labels, assignees, and messages.
CI/CD operations: Check pipeline status, watch pipelines, trace job logs, lint CI configuration, trigger and retry pipelines, and handle artifacts and debugging via API.
Direct API usage: Run targeted GitLab REST calls (with pagination guidance) when CLI commands aren’t enough.

Quick Start

Run glab auth login to authenticate, then use glab mr create --title "Fix bug" --description "Closes #123" --remove-source-branch --squash-before-merge to open a merge request with guarded merge settings.

Frequently Asked Questions about glab-cli

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

FAQPage Schema

How do I manage GitLab merge requests from the terminal?▼

You can manage GitLab merge requests from the terminal using the glab CLI to create, view, checkout, approve, and merge MRs with recommended safety flags like --remove-source-branch and --squash-before-merge for secure lifecycle handling.

Can I monitor and debug GitLab CI/CD pipelines without the web UI?▼

Yes, you can monitor and debug GitLab CI/CD pipelines without the web UI by using terminal commands to check pipeline status, watch live runs, trace job logs, lint CI configuration, and trigger or retry failed pipelines directly.

Does the glab CLI work with self-hosted GitLab instances?▼

Yes, the glab CLI works with both hosted and self-hosted GitLab instances. You must authenticate using glab auth login and scope your commands correctly via the -R flag to target the specific repository.

How do I make direct GitLab REST API calls with pagination from the command line?▼

You can make direct GitLab REST API calls from the command line when CLI commands are insufficient, using machine-friendly JSON outputs and embedding API pagination parameters directly in your URLs to manage large responses.

What is the best way to create a GitLab issue with labels and assignees from the CLI?▼

The best way to create a GitLab issue from the CLI is using glab commands to list, close, and update issues while applying labels, assignees, and messages directly through terminal-driven workflows.

Why should I use specific safety flags when merging a GitLab MR via CLI?▼

You should use safety flags like --squash-before-merge and --remove-source-branch when merging a GitLab MR via CLI to ensure pipeline-aware merging, prevent clutter, and maintain a clean commit history across terminal-driven workflows.