gitlab-operations

Operate GitLab repositories, merge requests, CI pipelines, and issues via glab CLI and MCP tools.

2|Updated Oct 20, 2017

Search Tags:#mcp #gitlab #merge requests #glab #self-hosted #commit investigation #ci pipelines

One-click install

npx skills add https://github.com/rbudiharso/dotfiles --skill gitlab-operations-rbudiharso

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-operations
Source: https://github.com/rbudiharso/dotfiles/tree/main/hermes/.hermes/skills/gitlab/gitlab-operations
Command: npx skills add https://github.com/rbudiharso/dotfiles --skill gitlab-operations-rbudiharso

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with GitLab through the glab CLI or MCP tools often fails silently against self-hosted instances because commands default to gitlab.com, and common tasks like tracing a broken deployment back to its source commit require knowing the right API endpoints and flags. ## Core Features & Use Cases - Repository and MR operations: View repo metadata, list merge requests, check CI pipeline status, and manage issues using `mcpgitlabglab_*` tools or terminal commands. - Self-hosted instance targeting: Use the full URL form `gitlab.gift.id/<group>/<project>` to avoid 401 errors caused by glab defaulting to gitlab.com. - Commit investigation: Trace a crashing pod's image tag (commit SHA) back to its diff, pipeline status, and job logs via `glab api` to find what broke a deployment. - Use Case: A pod is in CrashLoopBackOff with `Cannot find module X`. Look up the image tag SHA with `glab api`, inspect the commit diff for a `package.json` dependency change, and check whether the CI pipeline actually passed. ## Quick Start Ask the agent to view the repository gitlab.gift.id/infra/tada-prd-manifests and list its open merge requests using the GitLab tools.

Frequently Asked Questions about gitlab-operations

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

FAQPage Schema

How do I use glab CLI with a self-hosted GitLab instance?▼

Pass the full URL form like `gitlab.gift.id/<group>/<project>` as the repository argument instead of a bare group/project path. Without it, glab defaults to gitlab.com and returns 401 even when `glab auth status` shows the self-hosted instance is authenticated.

How do I trace a failed deployment back to its source commit in GitLab?▼

Take the commit SHA from the image tag, then run `glab api projects/<id>/repository/commits/<sha>` for commit details and append `/diff` to see changed files. Check `last_pipeline.status` and fetch job logs via `glab api projects/<id>/jobs/<job-id>/trace`.

Why does glab return 401 Unauthorized even though I am logged in?▼

The command almost certainly targeted gitlab.com instead of your self-hosted instance, since glab's default host is gitlab.com. Run `glab auth status` to confirm configured instances, then retry with the full host URL or `--hostname` flag.

Can glab repo search find projects on a self-hosted GitLab?▼

No, `glab repo search` has no host override and always queries gitlab.com, and the MCP search tool may return empty for self-hosted instances. Use `glab api "projects?search=<term>"` in the terminal instead.

How do I add the GitLab MCP server to Hermes?▼

Run `hermes mcp add gitlab --command glab --args mcp serve` after authenticating glab. In non-interactive contexts, pipe confirmation with `echo "Y" | hermes mcp add ...` so the tool-enable prompt is auto-accepted.

Why does glab api reject the --per-page flag?▼

`--per-page` is not a valid glab flag. Pass pagination as a query parameter in the URL instead, for example `glab api "projects?per_page=10"`.