gitlab-explorer

Explore GitLab repositories, merge requests, and CI/CD pipelines using glab and git.

112|26|Updated Jan 25, 2026

Search Tags:#issues #gitlab #ci-cd #glab #git-commands #repository-exploration #merge-requests

One-click install

npx skills add https://github.com/Yambr/openwebui-computer-use-community --skill gitlab-explorer

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-explorer
Source: https://github.com/Yambr/openwebui-computer-use-community/tree/main/skills/public/gitlab-explorer
Command: npx skills add https://github.com/Yambr/openwebui-computer-use-community --skill gitlab-explorer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires glab, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Explore GitLab repository exploration and management using glab and git commands, enabling quick access to repositories, merge requests, issues, and project structure while ensuring authentication beforehand.

Core Features & Use Cases

Discover and inspect repositories, clone projects, view merge requests, issues, and CI/CD status with glab and standard git commands.
Navigate project structures, search code, and audit history across GitLab groups and projects.

Quick Start

To begin, authenticate with your GitLab token and start exploring repositories using glab and git commands.

Frequently Asked Questions about gitlab-explorer

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

FAQPage Schema

How do I explore GitLab repositories using the command line?▼

You can explore GitLab repositories by executing glab and git commands to discover projects, inspect structures, and view merge requests across groups. This approach enables quick repository navigation and code searching directly from the terminal.

What do I need to check GitLab CI/CD pipelines and merge requests locally?▼

You need glab and jq installed to check GitLab CI/CD pipelines and merge requests locally. A pre-run script enforces authentication via your GitLab token, ensuring secure API access before executing any repository exploration commands.

Can I search code and audit history across multiple GitLab groups?▼

Yes, you can search code and audit history across multiple GitLab groups using glab API access. It allows you to navigate project structures, inspect repository contents, and track historical changes across your entire GitLab environment.

How do I clone a GitLab project and view its issues using glab?▼

To clone a GitLab project and view its issues, use glab commands for API access and git for local operations. This combination facilitates quick project cloning, issue inspection, and repository discovery without leaving the terminal.

Does this approach require a separate authentication step before exploring projects?▼

Yes, a pre-run script enforces authentication before exploring projects. This ensures your GitLab token is validated upfront, allowing glab to securely access the API for viewing merge requests, issues, and CI/CD status.

What is the best way to inspect GitLab project structures without a GUI?▼

The best way to inspect GitLab project structures without a GUI is using glab and standard git commands. This method allows you to perform repository discovery, code searching, and structural navigation efficiently across GitLab groups.