check-ci-health

Diagnose GitLab CI/CD pipeline failures by listing pipelines and retrieving trace logs.

2|Updated Feb 16, 2026

Search Tags:#automation #developer tools #ci/cd #debugging #pipeline #gitlab

One-click install

npx skills add https://github.com/dmzoneill/skills --skill check-ci-health

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: check-ci-health
Source: https://github.com/dmzoneill/skills/tree/main/check-ci-health
Command: npx skills add https://github.com/dmzoneill/skills --skill check-ci-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly identify and diagnose why their GitLab CI/CD pipelines are failing, reducing debugging time and improving code deployment efficiency.

Core Features & Use Cases

Pipeline Monitoring: Lists recent pipelines and their statuses (failed, success, running).
Failure Analysis: Retrieves details and trace logs for failing jobs to pinpoint errors.
Configuration Validation: Checks the .gitlab-ci.yml file for syntax errors.
Use Case: When a developer sees a red "X" on their merge request pipeline, they can use this Skill to understand which job failed, why it failed, and get suggestions for fixing it.

Quick Start

Use the check-ci-health skill to diagnose why the latest pipeline for the 'main' branch in the 'automation-analytics/automation-analytics-backend' project failed.

Frequently Asked Questions about check-ci-health

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

FAQPage Schema

How do I diagnose why a GitLab CI/CD pipeline is failing?▼

To diagnose GitLab CI/CD pipeline failures, you can list recent pipelines, identify failing jobs, and retrieve their trace logs to pinpoint exact errors. This requires GitLab API access and the specific project path.

How do I find which job caused my GitLab merge request pipeline to fail?▼

Finding the failed job in a GitLab merge request pipeline involves checking pipeline statuses and retrieving detailed trace logs for failing jobs. This pinpoints the exact job and provides context for the failure.

Can I validate my .gitlab-ci.yml configuration to find syntax errors?▼

Yes, you can validate the .gitlab-ci.yml file to check for syntax errors. This configuration validation helps identify structural issues in the file before or after a pipeline execution attempt.

What do I need to troubleshoot GitLab CI/CD pipeline issues?▼

Troubleshooting GitLab CI/CD pipeline issues requires GitLab API access and the specific project path. With these prerequisites, you can list pipelines and retrieve job trace logs for debugging.

Why does my GitLab pipeline fail with network issues and how do I fix it?▼

GitLab pipeline network issues can be diagnosed by retrieving trace logs from failing jobs. After identifying network errors in the logs, you can use suggestions to retry the pipeline or resolve the connectivity problem.

Does GitLab CI/CD debugging work for listing recent pipeline statuses like running or failed?▼

Yes, GitLab CI/CD debugging includes pipeline monitoring to list recent pipelines and display their current statuses, such as failed, success, or running, helping you track execution progress.