gha

Diagnose GitHub Actions workflow failures via gh CLI log analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzing GitHub Actions failures can be time-consuming and error-prone. This skill centralizes structured root-cause analysis using the gh CLI to speed up diagnosis and remediation.

Core Features & Use Cases

  • Root-cause Analysis: Identify the exact step or command causing a failure, with context from logs.
  • Flakiness Detection: Compare recent runs to determine if failures are sporadic or consistent.
  • Breaking Commit & Fix PR Detection: Pinpoint the commit introducing the failure and surface open PRs that fix it.
  • Scenario: Given a failing workflow run URL, quickly obtain a report outlining failure cause, affected jobs, and suggested next steps.

Quick Start

Use the gh CLI to inspect the provided workflow run URL and generate a structured failure report.

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 workflow failures using gh CLI?

Diagnose GitHub Actions workflow failures by sharing a failing workflow run URL to trigger structured root-cause analysis. The skill uses gh CLI to inspect logs, identify the breaking commit, and generate a diagnostic report outlining failure causes and next steps.

Can I detect flaky GitHub Actions runs by comparing recent workflow executions?

Yes, flakiness detection compares recent workflow runs to determine if failures are sporadic or consistent. This assesses run history to distinguish transient flakiness from persistent breaking changes in your GitHub Actions workflows.

Do I need gh CLI installed and authenticated to analyze GitHub Actions failures?

Yes, gh CLI must be installed and authenticated to analyze GitHub Actions failures. You also need access to the repository containing the failing workflow so the skill can inspect the run logs and generate a diagnostic report.

What is the best way to find the breaking commit and fix PRs for a failing GitHub Actions run?

The best way to find the breaking commit and fix PRs is providing the failing workflow run URL. The analysis pinpoints the specific commit introducing the failure and surfaces open pull requests that resolve the issue.

What does a GitHub Actions failure diagnostic report include?

A GitHub Actions failure diagnostic report includes the exact step or command causing the failure, affected jobs, log context, flakiness assessment, the breaking commit, and suggested next steps for remediation.