ci-failure-triage

Name: ci-failure-triage
Availability: InStock
Author: oalansilva

Classify CI failures by stage and error type with root-cause candidates.

Updated Dec 28, 2025

Search Tags:#troubleshooting #ci #root-cause-analysis #continuous-integration #build-failures #pipeline-stability

Ready to run

npx skills add https://github.com/oalansilva/crypto --skill ci-failure-triage-oalansilva

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-failure-triage
Source: https://github.com/oalansilva/crypto/tree/main/.codex/skills/infra/ci-failure-triage
Command: npx skills add https://github.com/oalansilva/crypto --skill ci-failure-triage-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI failures slow down delivery and degrade quality; this skill provides a structured triage to diagnose and stabilize pipelines quickly.

Core Features & Use Cases

Classify failures by stage and error type to target fixes.
Check for environment changes and test flakiness to distinguish flaky tests from real defects.
Propose fixes and temporary mitigations to reduce MTTR and restore confidence.
Output a triage summary with root-cause candidates for quick handoff.

Quick Start

Provide CI logs and recent changes to start the triage workflow.

Frequently Asked Questions about ci-failure-triage

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

FAQPage Schema

How do I troubleshoot continuous integration build failures and find the root cause?▼

To troubleshoot continuous integration build failures, you classify failures by stage and error type, then incorporate recent merges and environment changes to identify root causes and produce a triage summary with actionable mitigations.

How do I identify flaky tests versus real code defects in a failing CI pipeline?▼

To identify flaky tests versus real code defects in a failing CI pipeline, you assess test flakiness alongside recent environment changes to distinguish intermittent failures from actual defects and target fixes accurately.

What is the best way to stabilize CI pipelines after a build failure?▼

The best way to stabilize CI pipelines after a build failure is to generate a triage summary with root-cause candidates and apply temporary mitigations or fixes to restore pipeline confidence and reduce delivery delays.

Can I use CI failure triage with only build logs, or do I need recent merge data too?▼

You can use CI failure triage with build logs, but providing recent merge data and environment changes is required to accurately identify root causes and distinguish code defects from infrastructure issues.

Why does classifying CI failures by stage help reduce mean time to recovery?▼

Classifying CI failures by stage helps reduce mean time to recovery by targeting fixes to the specific pipeline phase and error type, enabling faster handoff and immediate application of actionable mitigations.