diagnose-ci-failures

Diagnose CI failures for a PR and generate a remediation plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly diagnose CI failures on a pull request, extract relevant failure logs, and produce a structured remediation plan you can review before taking action.

Core Features & Use Cases

  • CI failure detection: identify failing checks across a PR and summarize their status.
  • Log extraction and analysis: pull failure messages, stack traces, and root causes from CI runs.
  • Actionable remediation plan: generate a plan detailing categories of issues (formatting, linting, compilation, tests) and concrete next steps for fixes.

Quick Start

Ask the agent to diagnose CI for the current PR and return a structured remediation plan.

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 pull request?

To diagnose CI failures on a GitHub pull request, this tool collects PR status, extracts failure logs, and categorizes errors like formatting, linting, compilation, and tests. It then generates a structured remediation plan.

How do I extract error logs from failing CI checks across multiple environments?

Extracting error logs from failing CI checks is handled by querying PR data via the GitHub CLI. The tool analyzes these logs across multiple environments to pull failure messages, stack traces, and root causes.

Can I generate a remediation plan for failing CI checks before taking action?

Yes, you can generate a remediation plan for failing CI checks. The plan details categories of issues and concrete next steps, providing an actionable document you can review before applying fixes.

What categories of CI errors can be identified from pull request logs?

CI errors identified from pull request logs include formatting, linting, compilation, and test failures. The tool performs error categorization to summarize actionable fixes for these specific issue types.

Do I need the GitHub CLI to analyze CI failures for a PR?

Yes, you need the GitHub CLI installed to analyze CI failures for a PR. The tool requires the gh command line interface to query PR data, collect CI status, and extract the relevant failure logs.

Why does my CI remediation plan reference fix-errors guidance?

Your CI remediation plan references fix-errors guidance because the output plan document is structured to point toward concrete resolution steps. It categorizes errors first, then directs you to apply the fixes.