Actions Failure Analyzer

Actions Failure Analyzer is a DevOps skill for Claude Code, published by ykdojo in claude-code-tips.

9.6K stars764 forkson ykdojo/claude-code-tipsAdded 2026/08/15Repository updated 2026/08/06

agenticagentic-aiagentic-codingagentic-workflowaiclaudeclaude-aiclaude-codeclideveloper-toolsproductivitytips-and-tricks

Install in seconds

Install Actions Failure Analyzer

Copy Actions Failure Analyzer into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/ykdojo/claude-code-tips/tree/main/skills/gha ~/.claude/skills/gha

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/ykdojo/claude-code-tips.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/gha/SKILL.md in ykdojo/claude-code-tips
Installs to: ~/.claude/skills/gha
Collection: One of 9 skills cataloged from this repository
Category: DevOps — 798 skills

What Actions Failure Analyzer does

Actions Failure Analyzer investigates a failed GitHub Actions workflow run and identifies the specific root cause. It checks the job's recent history for flakiness, traces the breaking commit, and searches for open PRs that may already fix the issue.

Actions Failure Analyzer is cataloged under DevOps on DirSkills. Actions Failure Analyzer comes from a repository tagged agentic, agentic-ai, agentic-coding, agentic-workflow and ai.

Documentation

README

Excerpt

Investigate this GitHub Actions URL: $ARGUMENTS

Use the gh CLI to analyze this workflow run. Your investigation should:

Get basic info & identify actual failure:
- What workflow/job failed, when, and on which commit?
- CRITICAL: Read the full logs carefully to find what SPECIFICALLY caused the exit code 1
- Distinguish between warnings/non-fatal errors vs actual failures
- Look for patterns like "failing:", "fatal:", or script logic that determines when to exit 1
- If you see both "non-fatal" and "fatal" errors, focus on what actually caused the failure

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Actions Failure Analyzer

What else does ykdojo publish alongside Actions Failure Analyzer?
Actions Failure Analyzer is one of 9 skills that DirSkills catalogs from ykdojo/claude-code-tips, the repository it ships in. Its siblings there include HN Summarize, Half Clone and Handoff. Each one is a separate skill with its own page in this directory, installs the same way Actions Failure Analyzer does, and is maintained by ykdojo in that same repository. The rest of the collection is listed on the ykdojo/claude-code-tips page.
How does Actions Failure Analyzer compare to other DevOps skills?
Actions Failure Analyzer ranks #118 by stars among the 798 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Actions Failure Analyzer against them. Open each page to compare what they document and how they install.