gha

Diagnose GitHub Actions workflow failures and identify breaking commits.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill gha-toanpv90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gha
Source: https://github.com/ToanPV90/dotfiles/tree/main/claude/.claude/skills/gha
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill gha-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand why a GitHub Actions workflow run failed and what change most likely introduced the problem.

Core Features & Use Cases

  • Structured failure forensics: Uses the gh CLI to inspect the failed run, pull decisive log lines, and confirm the actual trigger for exit code 1.
  • Flakiness detection: Compares recent executions of the exact failing job to determine whether the issue is recurring or one-off.
  • Breaking commit identification: Locates the boundary between passing and failing runs and verifies the introduced commit for high confidence.
  • Fix discovery: Searches open pull requests for existing work that already addresses the failure signals, avoiding redundant recommendations.

Quick Start

Send a failing GitHub Actions run URL and ask the AI to diagnose the root cause, check flakiness, find the breaking commit if possible, and report whether an open fix PR exists.

Frequently Asked Questions about gha

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

FAQPage Schema
How do I find the breaking commit that caused a GitHub Actions workflow run to fail?

To find the breaking commit in GitHub Actions, the Skill analyzes the boundary between passing and failing runs using the `gh` CLI. It verifies the specific introduced commit to pinpoint the exact change that triggered the CI failure with high confidence.

What is the best way to check if a GitHub Actions failure is caused by test flakiness?

Checking GitHub Actions flakiness involves comparing recent executions of the exact failing job. The Skill uses `gh` run inspection to determine whether the failure is a recurring flakiness issue or a one-off event caused by a specific commit.

How do I diagnose the root cause of a GitHub Actions failure from the run URL?

Diagnosing a GitHub Actions failure from a run URL requires log-driven analysis. The Skill extracts decisive log lines via the `gh` CLI to confirm the actual trigger for exit code 1 and produces a structured report with the root cause and recommendations.

Can I search for an existing fix PR for a failing GitHub Actions workflow run?

Yes, you can search for an existing fix PR for failing GitHub Actions workflows. The Skill uses `gh` PR search to scan open pull requests for existing work that already addresses the failure signals, preventing redundant debugging efforts.

Does GitHub Actions log analysis work without installing additional CI debugging tools?

GitHub Actions log analysis works using the official `gh` CLI without needing additional CI debugging tools. It inspects the failed run, pulls decisive log lines, and assesses flakiness across recent runs directly through the GitHub command line interface.

What should I provide to start CI debugging on a failing GitHub Actions workflow run?

To start CI debugging on a failing GitHub Actions workflow run, you need to provide the failing run URL. The Skill uses this context to perform log-driven diagnosis, flakiness assessment, and breaking commit identification.