pipeline-debugger
Debug and monitor GitLab CI/CD pipelines for merge requests. Check pipeline status, view job logs, and troubleshoot CI failures. Use this when the user needs to investigate GitLab CI pipeline issues, check job statuses, or view specific job logs.
When & Why to Use This Skill
The GitLab CI Debugger skill empowers Claude to monitor and troubleshoot GitLab CI/CD pipelines efficiently. It automates the process of checking pipeline statuses, identifying failed jobs, and retrieving detailed logs, enabling developers to diagnose and resolve integration issues faster without leaving their development environment.
Use Cases
- Troubleshooting failed Merge Request pipelines by analyzing specific job logs and identifying root causes of build errors.
- Monitoring real-time pipeline status for feature branches to ensure continuous integration health before merging.
- Debugging complex CI failures by retrieving logs from specific pipeline IDs to pinpoint environment-specific configuration issues.
- Streamlining DevOps workflows by using natural language to query job statuses and receive actionable fix suggestions for CI/CD bottlenecks.
| name | pipeline-debugger |
|---|---|
| description | Debug and monitor GitLab CI/CD pipelines for merge requests. Check pipeline status, view job logs, and troubleshoot CI failures. Use this when the user needs to investigate GitLab CI pipeline issues, check job statuses, or view specific job logs. |
| allowed-tools | Bash, Read |
GitLab CI Debugger
This skill enables Claude to investigate GitLab CI pipeline failures by:
- Checking the current pipeline status for a branch, merge request, or a specific pipeline ID
- Identifying failed jobs
- Retrieving failed job logs
- Analyzing error messages and suggesting fixes
Prerequisites
- Git repository with GitLab remote configured
- GitLab authentication via GITLAB_TOKEN env var or .netrc file
The script will fail if it detects any missing configuration. Interpret the error message and provide instructions for setting up the required configuration.
Instructions
IMPORTANT: Always run the script from the user's current working directory (where Claude was launched), NOT from the
skill directory. The script needs access to the git repository context. Use the base directory (<base_path>) for this
skill to execute the script with an absolute path.
When the user asks to check CI status, debug pipeline failures, or view job logs:
Check Current Pipeline Status
- Run
<base_path>/scripts/check_pipeline.pywithout arguments to check the current branch's pipeline status - The script will display all jobs grouped by stage with status indicators
- Run
Check Specific Branch
- If the user asks to check on the pipeline status for a different branch than the current one, use the
-bor--branchoption to specify that branch.- Example:
<base_path>/scripts/check_pipeline.py -b feature-branch
- Example:
- If the user asks to check on the pipeline status for a different branch than the current one, use the
Check Specific Pipeline by ID
- If the user provides a pipeline ID directly, use the
-por--pipeline-idoption to inspect that pipeline - This skips the merge request lookup and directly inspects the specified pipeline
- Example:
<base_path>/scripts/check_pipeline.py -p 12519874995 - Note:
--pipeline-idand--branchare mutually exclusive
- If the user provides a pipeline ID directly, use the
View Job Logs
- Use the
-jor--joboption to retrieve and display logs for a specific job - Example:
<base_path>/scripts/check_pipeline.py -j "test-job-name" - Can be combined with any of the above options (branch, pipeline ID, or current branch)
- The script will show the job's metadata and full log output
- Use the
Troubleshoot CI Failures
- If the user asks to troubleshoot a CI failure, use the full log output of a job to identify the error and suggest fixes.