debug-ci-failure

Debug failed GitHub Actions CI runs by identifying the failed stage and root cause.

2|Updated Aug 18, 2025

Search Tags:#workflow #testing #debugging #troubleshooting #github actions #ci

Ready to run

npx skills add https://github.com/ESO-Toolkit/eso-toolkit --skill debug-ci-failure

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-ci-failure
Source: https://github.com/ESO-Toolkit/eso-toolkit/tree/main/.github/skills/debug-ci-failure
Command: npx skills add https://github.com/ESO-Toolkit/eso-toolkit --skill debug-ci-failure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic approach to diagnose and resolve failures in GitHub Actions CI runs, ensuring your code integrates smoothly and preventing PR blocks.

Core Features & Use Cases

Automated Triage: Identifies the specific failed job and extracts precise error messages from CI logs.
Root Cause Analysis: Guides you through common failure categories (formatting, linting, type errors, tests, build issues) with targeted commands.
Local Reproduction & Fix: Enables quick local verification and fixing of identified issues.
Use Case: When a pull request fails its CI checks, use this Skill to pinpoint the exact TypeScript error, fix it locally, and push the corrected code.

Quick Start

Use the debug-ci-failure skill to find the exact error message from the last failed CI run on the current branch.

Frequently Asked Questions about debug-ci-failure

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

FAQPage Schema

How do I debug a failed GitHub Actions CI run on my pull request?▼

Debugging a failed GitHub Actions CI run involves identifying the failed job, fetching logs, and extracting the exact error message. This workflow guides you through finding the root cause and reproducing the failure locally for a fast fix.

What is the best way to find the exact error message from a failed CI run?▼

The best way to find the exact error message from a failed CI run is through automated triage. This process examines the CI logs to pinpoint the specific failed stage and extract the precise error text needed for root cause analysis.

How do I reproduce a GitHub Actions failure locally to verify a fix?▼

To reproduce a GitHub Actions failure locally, you first extract the specific error text from the CI logs to understand the failure category. You then run the targeted commands locally to replicate the issue and verify your fix before pushing.

Does this CI troubleshooting workflow support identifying different types of build errors?▼

Yes, this CI troubleshooting workflow supports identifying different types of build errors. It guides you through common failure categories including formatting, linting, type errors, tests, and build issues with targeted commands for each.

Why does my CI run fail on a branch and how do I pinpoint the root cause?▼

Your CI run fails on a branch due to issues like formatting, type errors, or test failures. You pinpoint the root cause by analyzing the fetched CI logs to locate the exact error text, then reproducing the issue locally to fix it.