Verified:GitHub

glab

Manage GitLab issues and merge requests using the glab CLI.

9|Updated Jul 17, 2026

Search Tags:#git #code review #cli #issue tracking #gitlab #merge request #glab

One-click install

npx skills add https://github.com/Yassimba/loom --skill glab-yassimba

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: glab
Source: https://github.com/Yassimba/loom/tree/main/skills/glab
Command: npx skills add https://github.com/Yassimba/loom --skill glab-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires glab.

What problem does it solve? Working with GitLab issues and merge requests through the web UI interrupts a coding workflow. This Skill lets an agent create, read, update, and close GitLab issues and merge requests directly from the terminal using the glab CLI, with consistent branch naming and commit conventions. ## Core Features & Use Cases - Merge Request Management: Create feature branches, commit with conventional prefixes, and open merge requests with explicit target branches, self-assignment, and draft support. - Issue Operations: Create, view, comment on, label, and close GitLab issues from the command line. - Authentication & Verification: Check glab authentication status before write operations and verify MR pipeline status after opening. - Use Case: After finishing a bug fix, ask the agent to commit on a fix/ branch and open a merge request targeting main with a structured summary, then record the MR URL and check its pipeline. ## Quick Start Use the glab skill to create a merge request for my current changes targeting the main branch.

Frequently Asked Questions about glab

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

FAQPage Schema

How do I create a GitLab merge request from the command line?▼

Use glab mr create with a title, description, target branch, and assignee. First create a feature branch, commit your changes, push to origin, then run glab mr create --target-branch main --assignee @me to open the merge request.

How to create and manage GitLab issues with glab CLI?▼

Use glab issue create with a title and description to open issues. View them with glab issue view, add comments with glab issue note, apply labels with glab issue update --label, and close them with glab issue close.

Does glab require authentication before running commands?▼

Yes, glab requires authentication for write operations. Run glab auth status to verify your credentials before creating issues or merge requests. If authentication fails, stop and re-authenticate rather than exposing tokens in commands.

What branch naming conventions should I use for merge requests?▼

Use short prefixed branch names like feat/short-desc, fix/short-desc, or chore/short-desc. Match the MR title with conventional commit prefixes such as feat:, fix:, chore:, refactor:, or docs: for consistency.

Why should I avoid force-pushing to main in GitLab?▼

Force-pushing to main rewrites shared history and can break other contributors' work and pipelines. This workflow never force-pushes to main; instead it creates feature branches and merges them through reviewed merge requests.