Verified:GitHub

gitlab-ci-debugger

Diagnose GitLab CI/CD pipeline failures and fetch job logs for merge requests.

Updated Aug 23, 2026

Search Tags:#automation #debugging #logs #gitlab #ci-cd #pipelines #merge-request

One-click install

npx skills add https://github.com/mprpic/claude-gitlab-tools --skill gitlab-ci-debugger

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-ci-debugger
Source: https://github.com/mprpic/claude-gitlab-tools/tree/main/skills/gitlab-ci-debugger
Command: npx skills add https://github.com/mprpic/claude-gitlab-tools --skill gitlab-ci-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-gitlab>=4.0.0, and includes scripts (resource) components.

What problem does it solve?

This Skill enables you to debug and monitor GitLab CI/CD pipelines associated with merge requests directly from Claude. Check pipeline status, view job information grouped by stage, and fetch logs to troubleshoot failures without leaving your terminal.

Core Features & Use Cases

MR-focused pipeline visibility: See all jobs for the current MR, grouped by stage with clear status indicators.
On-demand job logs: Retrieve full logs for a selected job to quickly identify failures.
Actionable troubleshooting: Analyze errors in logs and surface recommended fixes to expedite resolution.

Quick Start

Use the script to check the current MR pipeline status:

Run: ./check_mr_pipeline.py
If you work on a different branch: ./check_mr_pipeline.py -b feature-branch
To view a specific job's log: ./check_mr_pipeline.py -j "job-name"

Frequently Asked Questions about gitlab-ci-debugger

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

FAQPage Schema

How do I debug a failed GitLab CI pipeline from the command line?▼

Debugging GitLab CI pipelines involves checking pipeline status, identifying failed jobs grouped by stage, and retrieving full logs for troubleshooting. This Skill fetches merge request pipeline data and surfaces job logs directly in your terminal using GitLab API authentication, letting you diagnose errors without switching tools.

Can I view GitLab CI job logs without accessing the web interface?▼

Yes. This Skill retrieves full logs for any job in your merge request pipeline through the terminal. Specify a job name with the -j flag to pull its complete output and analyze errors in-place, eliminating the need to navigate the GitLab UI.

What authentication do I need to access GitLab CI pipeline information?▼

You need GitLab authentication via a GITLAB_TOKEN environment variable or a .netrc file configured with your GitLab credentials. The Skill uses the python-gitlab library to connect securely and fetch pipeline and job data for your merge requests.

How do I check the pipeline status for a specific branch?▼

Run the check_mr_pipeline.py script with the -b flag followed by your branch name to view all jobs for that branch's merge request, grouped by stage with status indicators. This lets you monitor pipelines across different features without checking out each branch.

Can I use this to monitor pipelines across multiple merge requests?▼

This Skill is designed for the current merge request or a specified branch. It provides focused visibility into a single MR's pipeline status, jobs, and logs rather than cross-MR monitoring or aggregate pipeline reporting.

What GitLab versions and project types does this work with?▼

This Skill applies to GitLab-hosted projects and their merge requests. It uses the python-gitlab library (>=4.0.0) to interact with GitLab's API, making it compatible with supported GitLab instances where you have API access and valid authentication.