ci-failure-triage

Diagnose failing CI runs, repair confirmed causes, and verify fixes with local validation.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill ci-failure-triage-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-failure-triage
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/ci-failure-triage
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill ci-failure-triage-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Failing CI pipelines produce noisy logs and ambiguous signals, making it hard to find the first causal failure and fix it without masking real problems or prematurely claiming success. ## Core Features & Use Cases - Failure Classification: Separates actionable failures from cancelled, skipped, or external checks, then classifies them as product code, test, workflow, dependency, flaky, or infrastructure issues. - Bounded Repair with Verification: Reproduces the failure locally, applies the smallest scoped repair, adds regression tests, and validates before any remote recheck. - Approval-Gated Remote Actions: Requires explicit approval before remote reruns, workflow mutations, merges, or deployments, and never reports a local pass as hosted CI success. - Use Case: A pull request test job fails on GitHub Actions. The skill resolves the exact run and revision, extracts the failing log section, reproduces the defect locally, adds a regression test, applies the fix, and records the remote rerun as pending approval. ## Quick Start Ask the agent to triage the failing CI run on your pull request, diagnose the root cause, and propose a verified fix.

Frequently Asked Questions about ci-failure-triage

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

FAQPage Schema
How do I diagnose a failing CI pipeline run?

Resolve the exact run, job, and source revision, then retrieve only the relevant log sections to find the failing command and first causal error. Classify the failure as product code, test, workflow, dependency, flaky, or external before attempting any repair.

How to fix a failing pull request check in CI?

Reproduce the failure locally, apply the smallest source, test, or workflow repair, and add a regression test if the failure reflects a real defect. Run focused local validation, then request a remote recheck only with explicit approval.

Can this skill rerun CI jobs or merge pull requests automatically?

No. Remote reruns, workflow mutations, merges, deployments, and external comments all require explicit approval. Without approval, the remote recheck is recorded as pending and CI success is never claimed.

When should I not use CI failure triage?

Do not use it for local-only test failures or general workflow design work. It is scoped to failing hosted pipelines where a specific run, revision, and failing check can be resolved through provider APIs.

What happens when a CI failure is caused by an external outage?

External service failures are classified as external infrastructure issues and reported with a blocked status. The skill does not change repository code to mask failures caused by third-party outages.