Agent skill

GitHub Actions Failure Analysis

by ykdojo in ykdojo/claude-code-tips

Investigates a failed GitHub Actions run from its URL: pinpoints the real failure, checks the job's history for flakiness, and finds the breaking commit and any existing fix PR.

Custom licenceAuto-check passedDevOps & Cloud

Install GitHub Actions Failure Analysis

skills CLI
$ npx skills add ykdojo/claude-code-tips --skill gha -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ykdojo/claude-code-tips gha --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ykdojo/claude-code-tips.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gha .claude/skills/gha && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gha
GitHub stars
10k
Token cost
~639 tokens
SKILL.md length
380 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
Custom licence

At a glance

Investigates a failed GitHub Actions run from its URL: pinpoints the real failure, checks the job's history for flakiness, and finds the breaking commit and any existing fix PR.

  • Works in 5 steps: Get basic info & identify actual failure → Check flakiness: Check the past 10-20… → Identify breaking commit (if there's a… → …
  • Figuring out why a GitHub Actions workflow run failed
  • Calls gh
  • Deciding whether a CI failure is flaky or a regression

What it does

Given a workflow run URL, the agent uses the gh CLI to read the full logs and find what specifically caused the non-zero exit, separating warnings and non-fatal errors from the real failure. It then checks the history of the exact job that failed, over roughly the past 10 to 20 runs, to tell a one-off from a recurring pattern and to see the recent success rate and when it last passed.

If failures follow a pattern, it identifies the first failing and last passing run, names the commit that introduced the problem and verifies it by checking that the job fails after it and passes before. It then proposes a root cause checked against the logs and searches open pull requests for an existing fix. The final report covers the failure summary, flakiness, breaking commit, root cause analysis, any fix PR with its link and a recommendation, which is skipped when a fix PR already exists.

When your agent uses it

  • Figuring out why a GitHub Actions workflow run failed
  • Deciding whether a CI failure is flaky or a regression
  • Finding which commit broke a specific CI job
  • Checking whether a fix PR for a failing workflow already exists

Example prompts

  • “Investigate the failing deploy workflow on main and tell me whether it is flaky.”
  • “Find the commit that first broke the lint job in our CI.”
  • “Check if there is already an open PR fixing the failing integration-test job.”

Requirements

  • GitHub CLI (gh), authenticated for the repository

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Get basic info & identify actual failure
  2. Check flakiness: Check the past 10-20 runs of THE EXACT SAME failing job
  3. Identify breaking commit (if there's a pattern of failures for the specific job)
  4. Root cause: Based on logs, history, and any breaking commit, what's the likely cause?
  5. Check for existing fix PRs: Search for open PRs that might already address this issue

What it can do on your machine

Read from SKILL.md and the folder at commit 577ac89. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Actions Failure Analysis loads about 639 tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 380 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~15
When it runs · the whole SKILL.md, loaded when a task matches
~639

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 380 words (~639 tokens).

“Investigate this GitHub Actions URL: $ARGUMENTS”

— opening of SKILL.md by ykdojo, Custom licence
name
gha
argument-hint
<url>

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills/gha of ykdojo/claude-code-tips.

Open the folder on GitHubat commit 577ac89

Compare with similar skills

GitHub Actions Failure Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Actions Failure Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Actions Failure Analysis this skillykdojo/claude-code-tips10k—~639Automated safety check: PassCustom licence
gh-aw Workflow Diagnosisgithub/gh-aw5.4k—~4kAutomated safety check: PassMIT
CI/CD Failure Troubleshootingruby-git/ruby-git1.8k—~1.9kAutomated safety check: PassMIT
Megatron-LM CI Failure TriageNVIDIA/Megatron-LM18k—~1.6kAutomated safety check: PassApache-2.0
Debugging Workflowsgithub/gh-aw-firewall148—~2.7kAutomated safety check: NotesMIT
Debugging CI FailuresPostHog/posthog40k—~5.7kAutomated safety check: PassCustom licence

Similar skills

  • Official

    Guides your agent through diagnosing failed GitHub Agentic Workflows by downloading run logs, auditing individual runs and reading the artifacts they leave behind.

    5.4k GitHub stars~4k tokensUpdated today
    DevelopmentAuto-check passed
  • Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.

    1.8k GitHub stars~1.9k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed
  • Official

    Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.

    18k GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Debugging Workflows

    github/gh-aw-firewall

    Official

    Debug GitHub Actions workflows by downloading logs, analyzing summaries, and understanding how agentic workflows and the AWF firewall work together.

    148 GitHub stars~2.7k tokensUpdated today
    DevelopmentAuto-check: notes
  • Debugging CI Failures

    PostHog/posthog

    Official

    Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?").

    40k GitHub stars~5.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Authoring CI Workflows

    PostHog/posthog

    Official

    A skill your agent uses when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under .github/ — new CI jobs, triggers, matrices, checkout/clone tuning, action…

    40k GitHub stars~12k tokensUpdated today
    DevelopmentAuto-check passed

More from ykdojo/claude-code-tips

All 9 skills in this repo
  • Hacker News Summarizer

    ykdojo/claude-code-tips

    Fetches Hacker News top stories, a chosen story with its comment thread and the linked article through the official APIs, then summarizes them.

    10k GitHub stars~942 tokensUpdated 13 days ago
    Auto-check passed
  • Reddit JSON Fetcher

    ykdojo/claude-code-tips

    Fetches Reddit posts, threads and search results as JSON through a browser session, using a DuckDuckGo redirect to get past Reddit's automated-access block.

    10k GitHub stars~1.4k tokensUpdated 13 days ago
    Auto-check passed
  • Claude Code Version Check

    ykdojo/claude-code-tips

    Recommends whether to stay on the installed Claude Code version, update, or pin another one by comparing npm tags, release timing and the changelog.

    10k GitHub stars~1.8k tokensUpdated 13 days ago
    Auto-check passed
  • Private GitHub Repo Search

    ykdojo/claude-code-tips

    Full-text searches across every one of the user's GitHub repos, including private ones, using a local mirror and ripgrep instead of GitHub's own search.

    10k GitHub stars~444 tokensUpdated 13 days ago
    Auto-check passed
  • CLAUDE.md Review

    ykdojo/claude-code-tips

    Mines your recent Claude Code conversations for rules that were broken, missing or stale, and suggests edits to global and project CLAUDE.md files.

    10k GitHub stars~677 tokensUpdated 13 days ago
    Auto-check passed
  • Conversation Half-Clone

    ykdojo/claude-code-tips

    Clones only the later half of the current Claude Code session into a fresh one, cutting token usage while keeping the recent work intact.

    10k GitHub stars~372 tokensUpdated 13 days ago
    Auto-check passed

Questions about GitHub Actions Failure Analysis

What does GitHub Actions Failure Analysis do?

Investigates a failed GitHub Actions run from its URL: pinpoints the real failure, checks the job's history for flakiness, and finds the breaking commit and any existing fix PR. Given a workflow run URL, the agent uses the gh CLI to read the full logs and find what specifically caused the non-zero exit, separating warnings and non-fatal errors from the real failure. It then checks the history of the exact job that failed, over roughly the past 10 to 20 runs, to tell a one-off from a recurring pattern and to see the recent success rate and when it last passed.

When should I use GitHub Actions Failure Analysis?

GitHub Actions Failure Analysis fits situations like: figuring out why a GitHub Actions workflow run failed; deciding whether a CI failure is flaky or a regression; finding which commit broke a specific CI job; checking whether a fix PR for a failing workflow already exists.

How do I install GitHub Actions Failure Analysis in Claude Code?

Run `npx skills add ykdojo/claude-code-tips --skill gha -a claude-code`. Or copy the skill folder (skills/gha in ykdojo/claude-code-tips) into .claude/skills/gha in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Actions Failure Analysis in Codex?

Run `npx skills add ykdojo/claude-code-tips --skill gha -a codex`. Or copy the skill folder (skills/gha in ykdojo/claude-code-tips) into .agents/skills/gha in your project. Codex loads it when a task matches its description.

Can I use GitHub Actions Failure Analysis in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ykdojo/claude-code-tips --skill gha -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gha, .gemini/skills/gha, .github/skills/gha and .opencode/skills/gha in your project.

What does GitHub Actions Failure Analysis need to run?

Going by SKILL.md and its folder, GitHub Actions Failure Analysis needs the command-line tools its instructions call (gh). Our summary lists: GitHub CLI (gh), authenticated for the repository.

Does GitHub Actions Failure Analysis access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is GitHub Actions Failure Analysis safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Actions Failure Analysis use?

GitHub Actions Failure Analysis has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does GitHub Actions Failure Analysis use?

About 639 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub Actions Failure Analysis?

Skills that share tags, products or a category with GitHub Actions Failure Analysis: gh-aw Workflow Diagnosis (github/gh-aw, 5.4k stars), CI/CD Failure Troubleshooting (ruby-git/ruby-git, 1.8k stars), Megatron-LM CI Failure Triage (NVIDIA/Megatron-LM, 18k stars) and Debugging Workflows (github/gh-aw-firewall, 148 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Actions Failure Analysis?

ykdojo (a GitHub user) maintains it in ykdojo/claude-code-tips, which has 10,202 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on September 25, 2026.

Source: ykdojo/claude-code-tips on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.