gitlab-integration

Query GitLab projects, pipelines, merge requests, commits, and issues via REST API scripts.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill gitlab-integration-erwinv2k-tkg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitlab-integration
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/incidentfox/sre-agent/.claude/skills/vcs-gitlab
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill gitlab-integration-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, and includes scripts (resource) components.

What problem does it solve? Investigating GitLab activity during incident response or code review requires manually navigating the GitLab UI or writing ad-hoc API calls. This Skill provides ready-made scripts to inspect projects, CI/CD pipelines, merge requests, commits, branches, and issues directly from the command line. ## Core Features & Use Cases - Pipeline Failure Investigation: List failed pipelines and drill into individual job statuses, durations, and failure reasons to pinpoint broken builds. - Merge Request & Commit Analysis: Retrieve MR details, file-level diffs, and commit history with author and timestamp metadata for code review or deployment correlation. - Issue & Project Management: List and search projects, branches, and issues, and create new issues programmatically. - Use Case: During an incident, run the pipeline failure workflow to find the failed pipeline, inspect its jobs, then trace the responsible commit and merge request to identify the change that caused the outage. ## Quick Start Ask the agent to list the failed CI/CD pipelines for the project "mygroup/myapp" and show the jobs that failed in the most recent one.

Frequently Asked Questions about gitlab-integration

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

FAQPage Schema
How do I investigate a failed GitLab CI/CD pipeline from the command line?

Run get_pipelines.py with --status failed to list failing pipelines, then get_pipeline_jobs.py with the pipeline ID to see each job's status, duration, and failure reason. Follow up with get_commit.py to inspect the triggering commit.

How to get merge request diffs using the GitLab API?

Use get_mr_changes.py with the project path and MR IID. It calls the GitLab REST API v4 changes endpoint and returns per-file diffs with add, delete, rename, and modify flags, in JSON or human-readable output.

Does this work with self-hosted GitLab instances?

Yes. Set the GITLAB_URL environment variable to your instance URL; it defaults to https://gitlab.com. The client appends /api/v4 automatically, or uses GITLAB_BASE_URL directly in proxy mode.

Why is GITLAB_TOKEN not visible in environment variables?

Credentials are injected transparently by a proxy layer, so the token is intentionally not exposed to the scripts' environment. The client also supports SANDBOX_JWT or tenant/team headers as fallback authentication modes.

Can I create GitLab issues programmatically with Python?

Yes. Run create_issue.py with --project and --title, plus optional --description, --labels, and --assignee-ids. It posts to the GitLab issues API and returns the new issue IID and web URL.