glab

Query and monitor GitLab merge requests, pipelines, and issues from the CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/d3fvxl/.dotfiles --skill glab-d3fvxl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: glab
Source: https://github.com/d3fvxl/.dotfiles/tree/main/config/opencode-efg/skills/glab
Command: npx skills add https://github.com/d3fvxl/.dotfiles --skill glab-d3fvxl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables teams to audit and monitor GitLab activity from the command line while enforcing safety by requiring explicit approval before any state-changing operation.

Core Features & Use Cases

  • Read-only visibility into Merge Requests, Pipelines, Issues, and repository status.
  • Approval workflow for state-changing actions (create/merge/close/update) to prevent unintended changes.
  • Comprehensive Quick Reference of glab commands for easy operational guidance.

Quick Start

Run read-only queries on GitLab resources (MRs, pipelines, issues) and request explicit approval before making changes.

Frequently Asked Questions about glab

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

FAQPage Schema
How do I monitor GitLab merge requests and pipelines from the CLI safely?

You can monitor GitLab merge requests and pipelines from the CLI safely by running read-only queries that audit project activity. This approach provides visibility into repository status without executing state-changing operations.

Can I enforce an approval workflow before merging or closing GitLab issues via command line?

Yes, you can enforce an approval workflow before merging or closing GitLab issues via command line. The system requires explicit user approval prior to executing any state-changing actions to prevent unintended updates.

Do I need glab installed and authenticated to query GitLab merge requests?

Yes, you need glab installed and authenticated to query GitLab merge requests. Enforcing these prerequisites ensures secure access to your GitLab groups and projects for read-only audits and operational guidance.

What is the best way to audit GitLab repository status without making unintended changes?

The best way to audit GitLab repository status without unintended changes is using a read-only default behavior mode. This method queries issues and pipelines safely, requiring explicit prompts for any modifications.

Why are my state-changing GitLab commands prompting for approval?

State-changing GitLab commands prompt for approval to enforce safety and prevent unintended modifications. This explicit approval workflow applies to actions like creating, merging, closing, or updating resources within your projects.

Does this approach support read-only audits for GitLab groups and projects?

Yes, this approach supports read-only audits for GitLab groups and projects. It applies comprehensive visibility into merge requests, pipelines, and issues while maintaining safety by blocking automatic state changes.