diagnose-ci-failures

Extract CI error logs and generate fix plans for GitHub Actions failures.

144|16|Updated May 3, 2026
One-click install
npx skills add https://github.com/Terry-Mao/AICodingFlow --skill diagnose-ci-failures-terry-mao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-ci-failures
Source: https://github.com/Terry-Mao/AICodingFlow/tree/main/.agents/skills/diagnose-ci-failures
Command: npx skills add https://github.com/Terry-Mao/AICodingFlow --skill diagnose-ci-failures-terry-mao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automatically diagnoses CI failures in PRs, branches, or GitHub Actions runs, providing detailed error logs and a fix plan to resolve issues efficiently.

Core Features & Use Cases

  • CI Failure Diagnosis: Identifies and reports CI failures, whether they are from PRs, branches, or GitHub Actions runs.
  • Error Log Extraction: Extracts detailed error logs from the CI runs to aid in troubleshooting.
  • Fix Plan Generation: Generates a comprehensive plan to address the identified issues, ensuring a structured approach to resolving CI failures.
  • Use Case: If a PR fails during a GitHub Actions run, this Skill can diagnose the issue, provide the error logs, and suggest a plan to fix the problems.

Quick Start

To diagnose CI failures in the current branch, run the following command:

diagnose-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 GitHub Actions CI failures and generate a fix plan?

To diagnose GitHub Actions CI failures, this tool extracts error logs from CI runs and generates a structured fix plan. It handles PRs, branches, and run URLs to suggest resolutions.

Do I need the GitHub CLI to troubleshoot CI failures in PRs?

Yes, the GitHub CLI is required to troubleshoot CI failures in PRs. The diagnosis tool depends on it to access CI run details, extract logs, and generate a fix plan.

What inputs are supported for diagnosing CI failures in GitHub Actions?

Diagnosing CI failures supports GitHub Actions run URLs, branch names, or pull requests as inputs. This allows you to target specific CI troubleshooting scenarios directly from your repository.

What's the best way to extract error logs from a failed GitHub Actions run?

The best way to extract error logs is to run an automated diagnosis command that fetches failed GitHub Actions run details. It automatically pulls detailed error logs to aid in troubleshooting.

Can I automatically generate a fix plan for branch CI failures?

Yes, you can automatically generate a fix plan for branch CI failures. By providing the branch name, the tool identifies the failure, extracts logs, and suggests a structured resolution plan.