gha

Diagnose GitHub Actions job failures and identify root causes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the diagnosis of failing GitHub Actions workflows to identify the exact step and commit responsible for a failure, enabling faster remediation and less downtime.

Core Features & Use Cases

  • Identify the failing workflow, job, and commit from a given URL.
  • Check historical runs for the specific job to determine flakiness and recent success rate.
  • Surface the breaking commit, correlate with logs, and reference any open fix PRs if available.

Quick Start

Investigate the provided GitHub Actions URL using the gh CLI to identify the failing job, assess history for flakiness, and report root cause with remediation guidance.

Frequently Asked Questions about gha

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

FAQPage Schema
How do I diagnose GitHub Actions failures and find the root cause?

To identify a flaky GitHub Actions job, you check historical runs for that specific job to determine recent success rates and stability. This analysis applies to both single-workflow and multi-job scenarios to distinguish flakiness from consistent failures.

Can I use gh CLI to analyze failing workflow runs?

Yes, you can use gh CLI to parse full failure logs and compare run history for specific failing GitHub Actions jobs. This identifies the breaking commit, determines flakiness, and produces a structured report with remediation guidance.

What is the best way to find which commit broke a GitHub Actions workflow?

The best way to find a breaking commit is to analyze GitHub Actions failure logs and compare run history. This surfaces the exact commit responsible for the failure and references any open fix PRs if available.

Does GitHub Actions failure analysis work for multi-job scenarios?

Yes, GitHub Actions failure analysis applies to both single-workflow and multi-job scenarios to determine flakiness and stability. It identifies the specific failing job across runs and correlates it with the breaking commit.

Why does my GitHub Actions workflow keep failing intermittently?

Your GitHub Actions workflow may be failing intermittently due to flakiness, which you can determine by checking historical runs for the specific job. This analysis identifies recent success rates and distinguishes flaky jobs from consistently failing ones.