Verified:Website 𝕏@ProchazkaFilip GitHub

pipeline

Diagnose failed GitLab MR pipeline jobs by analyzing logs and proposing fixes.

15|1|Updated Jan 3, 2026

Search Tags:#ci/cd #debugging #pipeline #gitlab #merge request #glab #job logs

One-click install

npx skills add https://github.com/fprochazka/claude-code-plugins --skill pipeline-fprochazka

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/fprochazka/claude-code-plugins/tree/main/plugins/glab/skills/pipeline
Command: npx skills add https://github.com/fprochazka/claude-code-plugins --skill pipeline-fprochazka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a merge request pipeline fails on GitLab, finding the root cause means digging through job logs, test reports, and CI config output. This Skill triages failed CI jobs by reading a structured pipeline dump and proposing concrete fixes. ## Core Features & Use Cases - Guided failure triage: Reads the pipeline summary first, then only the logs of failed jobs, test reports, lint output, or downstream pipeline data as needed. - Structured dump inspection: Works with output from the glab-pipeline CLI, including summary.json, job logs, test-report.json, and merged.yml. - Job retry support: Retries failed jobs with glab ci retry and re-inspects the pipeline after retries or new pushes. - Use Case: An MR pipeline fails with three red jobs. Invoke this Skill to identify which job caused the failure, read its log tail, and get a proposed fix before touching any code. ## Quick Start Ask the assistant to analyze the current MR pipeline failures and propose fixes for the failed CI jobs.

Frequently Asked Questions about pipeline

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

FAQPage Schema

How do I debug a failed GitLab CI pipeline job?▼

Start with the pipeline summary file, which names each failed job, its stage, and failure reason. Then read only the failed job's log tail for script errors, or test-report.json for test failures, rather than grepping the full raw dump.

How to retry a failed GitLab CI job from the command line?▼

Use glab ci retry <job-name> to retry a failed job. The glab-pipeline tool only inspects pipelines and has no retry capability of its own, so retries go through the glab CLI.

Can I inspect a failed downstream child pipeline in GitLab?▼

Yes. Check the downstream/<bridge>-<id>.json file in the pipeline dump for the failed child pipeline, then recurse by running glab-pipeline inspect --pipeline-id <id> on that child pipeline.

Why does my GitLab CI include resolve differently on the source branch?▼

An include: directive can resolve differently depending on the branch context. Re-run the inspection with --with-merged-ci-config to see the merged.yml that GitLab actually parsed for that branch.

What if a test job failed but the test report is missing?▼

Re-run the pipeline inspection with the --with-test-report flag to fetch the missing report. The test-report.json file holds per-test results, which is faster than searching a long job trace.