Verified:GitHub

glab

Automate GitLab merge request, issue, pipeline, and project management via glab CLI.

Updated Aug 23, 2026

Search Tags:#cli #graphql #issues #gitlab #merge requests #ci #glab

One-click install

npx skills add https://github.com/led8/.codex --skill glab-led8

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes friction when interacting with GitLab from the command line by providing clear command patterns, API fallbacks, and troubleshooting guidance so users can list and manage merge requests, issues, pipelines, projects, and job logs efficiently.

Core Features & Use Cases

High-level glab command patterns for listing, viewing, creating, approving, and merging merge requests, and for listing and managing issues.
Pipeline and CI guidance that prefers GraphQL queries for reliable pipeline and job details, plus instructions to extract numeric IDs for retrieving job traces.
Direct API usage examples for complex queries, JSON output guidance for scripting, authentication flows (interactive and non-interactive), and common error handling scenarios.
Use case: a CI operator needs to find failed jobs for a merge request, extract job IDs via GraphQL, and fetch logs for debugging.

Quick Start

Ask the assistant to list open merge requests in owner/repo filtered by author alice and label bug and return the results in JSON for parsing.

Frequently Asked Questions about glab

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

FAQPage Schema

How do I list and manage GitLab merge requests from the command line?▼

To manage GitLab merge requests from the command line, use glab high-level command patterns to list, view, create, approve, and merge MRs. You can filter open merge requests by author or label and return the results in JSON for scripting.

What is the best way to fetch GitLab CI pipeline job logs for debugging?▼

The best way to fetch GitLab CI pipeline job logs is to query pipeline and job details using GraphQL, extract the numeric IDs from the returned GraphQL gid values, and then retrieve the specific job traces for debugging failed CI operations.

How do I authenticate glab for non-interactive CI environments?▼

To authenticate glab in non-interactive CI environments, use a GITLAB_TOKEN environment variable or configure glab auth with a token. This enables automated command-line access to retrieve and manage GitLab projects without interactive login prompts.

Can I use glab api for complex GraphQL queries on GitLab repositories?▼

Yes, you can use glab api to invoke direct REST and GraphQL queries for complex data retrieval across GitLab repositories. This approach provides JSON output guidance for scripting and allows precise automation of custom GitLab API interactions.

Does glab support listing and managing GitLab issues alongside merge requests?▼

Yes, glab supports listing and managing GitLab issues alongside merge requests. The CLI provides high-level commands to interact with issues, inspect pipelines, and fetch job logs across repositories, satisfying requirements for developers and release engineers.