Verified:GitHub

pipeline-triage

Diagnose GitLab CI pipeline failures and propose minimal safe fixes.

Updated May 6, 2026

Search Tags:#devops #debugging #root cause #pipeline #gitlab #triage #ci

One-click install

npx skills add https://github.com/UnionStreetAI/unionstreet --skill pipeline-triage-unionstreetai

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pipeline-triage
Source: https://github.com/UnionStreetAI/unionstreet/tree/main/plugins/gitlab/skills/pipeline-triage
Command: npx skills add https://github.com/UnionStreetAI/unionstreet --skill pipeline-triage-unionstreetai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a GitLab CI pipeline fails, engineers must manually dig through failed jobs, logs, artifacts, and recent commits to find the root cause. This Skill automates that investigation and summarizes the likely cause, the responsible owner, and the smallest safe fix. ## Core Features & Use Cases - Failure Inspection: Examines failed jobs, logs, and artifacts from GitLab CI pipelines to isolate what broke. - Change Correlation: Reviews recent changes to connect failures with the commits or merge requests that introduced them. - Actionable Summary: Produces a triage report naming the likely root cause, the owner, and the smallest safe fix. - Use Case: A merge request pipeline turns red overnight. Ask the agent to triage it, and receive a summary pointing to the failing job, the commit that caused it, and a suggested fix before your morning standup. ## Quick Start Triage the latest failed GitLab CI pipeline on my project and summarize the root cause, owner, and smallest safe fix.

Frequently Asked Questions about pipeline-triage

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

FAQPage Schema

How do I triage a failed GitLab CI pipeline?▼

Triage a failed GitLab CI pipeline by inspecting the failed jobs, their logs, and any artifacts, then correlating the failure with recent changes. This Skill automates that process and summarizes the likely root cause, owner, and smallest safe fix.

How to find the root cause of a GitLab pipeline failure?▼

Finding the root cause involves reading failed job logs, checking artifacts, and reviewing recent commits that may have introduced the breakage. The Skill performs this inspection and reports the most likely cause along with a proposed fix.

Can this Skill analyze GitHub Actions or Jenkins failures?▼

No, this Skill is scoped to GitLab CI pipelines. It inspects GitLab jobs, logs, artifacts, and recent changes, and does not cover other CI platforms such as GitHub Actions or Jenkins.

Does pipeline triage apply fixes automatically?▼

No, the Skill proposes the smallest safe fix rather than applying it. It summarizes the likely root cause and owner so a human can review and decide on the remediation.

What information does the pipeline triage summary include?▼

The summary includes the likely root cause of the failure, the owner responsible for the change, and the smallest safe fix. It is derived from failed jobs, logs, artifacts, and recent changes in the GitLab project.