diagnose-ci-failures

Diagnose GitHub PR CI failures and generate a fix plan.

37|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/terzigolu/warp-lite --skill diagnose-ci-failures-terzigolu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-ci-failures
Source: https://github.com/terzigolu/warp-lite/tree/main/.agents/skills/diagnose-ci-failures
Command: npx skills add https://github.com/terzigolu/warp-lite --skill diagnose-ci-failures-terzigolu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates diagnosing CI failures for a PR and producing a concrete fix plan.

Core Features & Use Cases

  • Deterministic workflow to verify PR existence, fetch CI status, and identify failing checks.
  • Failure log extraction and error categorization (formatting, linting, compilation, tests).
  • Output a prioritized fix plan with validation steps, designed to be reviewed before execution.
  • Guidance on possible follow-up actions and escalation using the fix-errors framework.

Quick Start

Run the diagnose-ci-failures skill on a PR to generate a plan for fixing CI failures.

Frequently Asked Questions about diagnose-ci-failures

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

FAQPage Schema
How do I diagnose CI failures on a GitHub PR?

To diagnose CI failures on a GitHub PR, this skill verifies the PR, fetches CI status, and extracts failing check logs to categorize errors and output a prioritized fix plan.

What is the best way to triage build and test failures across GitHub PRs?

The best way to triage build and test failures is to collect CI logs and categorize them by failure type, which this skill does to generate a concrete fix plan for review.

Does this CI failure diagnosis skill automatically apply code fixes to my PR?

No, this CI failure diagnosis skill does not automatically apply code fixes; it outputs a prioritized fix plan with validation steps designed to be reviewed before execution.

Do I need the gh CLI to extract PR failure logs?

Yes, you need the gh CLI installed, as this skill orchestrates gh CLI commands to verify PR existence, fetch CI status, and collect failure logs for error categorization.

What categories of CI errors can be identified from PR logs?

The categories of CI errors identified from PR logs include formatting, linting, compilation, and test failures, which are then used to generate a targeted fix plan.