gha

Analyze GitHub Actions run URLs to identify failing jobs and exit causes.

9.6k|760|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/ykdojo/claude-code-tips --skill gha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gha
Source: https://github.com/ykdojo/claude-code-tips/tree/main/skills/gha
Command: npx skills add https://github.com/ykdojo/claude-code-tips --skill gha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams quickly diagnose GitHub Actions failures by extracting failure context from logs, identifying the failing workflow and job, and pinpointing the exact exit condition.

Core Features & Use Cases

  • Root-cause analysis: Identify which workflow/job failed, when, and the exact exit reason from logs.
  • Flakiness assessment: Review recent runs for the same job to determine stability and recurring issues.
  • Remediation guidance: Propose likely root causes and check for open PRs addressing the issue.
  • Use Case: When a PR causes a CI failure in a workflow, quickly isolate the failing job and the breaking commit to speed up fixes.

Quick Start

Investigate GitHub Actions by providing the URL of the failing run or workflow to the agent and follow prompts to fetch logs and run history.

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 from workflow run logs?

To diagnose GitHub Actions failures, you provide the failing run URL to extract the failing workflow, specific job, and exact exit cause from logs. This isolates the breaking commit and speeds up fixes.

Can I assess GitHub Actions job flakiness using recent run history?

You can assess GitHub Actions job flakiness by reviewing the past 10 to 20 runs for the same job. This history assessment determines job stability and identifies recurring issues or breaking commit patterns.

Do I need the gh CLI to analyze GitHub Actions root causes?

You need the gh CLI and repository access to analyze GitHub Actions root causes. The CLI fetches the specific job run data and logs required to pinpoint the exact exit condition.

What's the best way to identify a breaking commit in a failing GitHub Actions workflow?

The best way to identify a breaking commit is analyzing the specific job's status and recent run history rather than the full workflow. This isolates the failing job and proposes likely root causes.

Why does my GitHub Actions workflow fail but not show the specific job error?

GitHub Actions workflow failures can hide specific job errors if you review the full workflow status instead of the specific job. Analyzing the exact job logs extracts the precise exit condition and remediation guidance.