github-ci-debug

Diagnose failing GitHub Actions runs and propose focused fixes from job and step evidence.

5.3k|976|Updated Aug 25, 2025
One-click install
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill github-ci-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-ci-debug
Source: https://github.com/Devin-AXIS/iPolloWork/tree/main/examples/plugin-packages/github/skills/github-ci-debug
Command: npx skills add https://github.com/Devin-AXIS/iPolloWork --skill github-ci-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a GitHub Actions check fails, developers waste time digging through run pages, job logs, and step output to find the root cause. This Skill automates that triage by pulling bounded run, job, and step evidence and turning it into a concrete diagnosis and fix proposal.

Core Features & Use Cases

  • Failure Diagnosis: Resolves the repository and Actions run ID from a URL, PR, or current branch, then retrieves failing jobs and steps through the connected GitHub service.
  • Root Cause Reporting: Reports the run URL, failing jobs, failing steps, and the most likely root cause supported by the returned evidence, while distinguishing external check providers from GitHub-controlled checks.
  • Optional Local Fix: When the requested task includes implementation, applies the smallest fix tied to the failing step in the local checkout and runs the relevant local check.
  • Use Case: A pull request shows a red CI check. Point the Skill at the PR, and it identifies the failing test step, explains the likely cause, and patches the broken test locally for you to verify.

Quick Start

Diagnose why the GitHub Actions run on my current pull request failed and propose a fix.

Frequently Asked Questions about github-ci-debug

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

FAQPage Schema
How do I debug a failing GitHub Actions workflow?

Provide the run URL, pull request, or current branch context, and the Skill resolves the repository and run ID, then calls the actions-failure capability through the connected GitHub service. It reports failing jobs, failing steps, and the most likely root cause from the returned evidence.

How to find the root cause of a failed CI check on a pull request?

The Skill retrieves bounded run, job, and step evidence for the PR's failing check and identifies the most likely root cause tied to the failing step. It then proposes the smallest fix directly connected to that step.

Can this Skill fix the failing CI check automatically?

It implements a fix locally only when the requested task explicitly includes implementation. After editing the local checkout, it runs the relevant local check to verify the change before summarizing remaining uncertainty.

Does it work with external CI providers like third-party status checks?

For checks belonging to external providers, the Skill reports the check's URL and states that the GitHub service does not control it. It does not attempt to diagnose or modify external provider runs.

What are the limitations of GitHub Actions failure diagnosis with this Skill?

It cannot rerun or cancel workflows, and it only sees the job and step summaries the service returns, not complete logs. It also avoids changing code when evidence points to infrastructure or flaky failures unless the user chooses that scope.