Automated diagnosis of GitHub Actions CI/CD failures.
Install
mkdir -p .claude/skills/gha && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4201" && unzip -o skill.zip -d .claude/skills/gha && rm skill.zipInstalls to .claude/skills/gha
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Analyze GitHub Actions failures and identify root causesKey capabilities
- →Extract specific exit code 1 triggers from GitHub Actions logs
- →Assess job flakiness by analyzing the last 10-20 runs of a specific job
- →Identify the specific commit that introduced a job failure
- →Search for existing open pull requests related to failure patterns
How it works
The tool uses the gh CLI to retrieve job logs and run history, then correlates failure patterns with commit history to isolate the root cause.
Inputs & outputs
When to use gha
- →Debugging CI/CD failures
- →Identifying flaky tests
- →Tracing breaking commits
- →Analyzing workflow logs
About this skill
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
-
Check flakiness: Check the past 10-20 runs of THE EXACT SAME failing job:
- IMPORTANT: If a workflow has multiple jobs, you must check history for the SPECIFIC JOB that failed, not just the workflow
- Use
gh run list --workflow=<workflow-name>to get run IDs, thengh run view <run-id> --json jobsto check the specific job's status - Is this a one-time failure or recurring pattern for THIS SPECIFIC JOB?
- What's the success rate for THIS JOB recently?
- When did THIS JOB last pass?
-
Identify breaking commit (if there's a pattern of failures for the specific job):
- Find the first run where THIS SPECIFIC JOB failed and the last run where it passed
- Identify the commit that introduced the failure
- Verify by checking: does THIS JOB fail in ALL runs after that commit? Does it pass in ALL runs before?
- If verified, report the breaking commit with high confidence
-
Root cause: Based on logs, history, and any breaking commit, what's the likely cause?
- Focus on what ACTUALLY caused the failure (not just any errors you see)
- Verify your hypothesis against the logs and failure logic
-
Check for existing fix PRs: Search for open PRs that might already address this issue:
- Use
gh pr list --state open --search "<keywords>"with relevant error messages or file names - Check if any open PR modifies the failing file/workflow
- If a fix PR exists, note it in your report and skip the recommendation section
- Use
Write a final report with:
- Summary of failure (what specifically triggered the exit code 1)
- Flakiness assessment (one-time vs recurring, success rate)
- Breaking commit (if identified and verified)
- Root cause analysis (based on the ACTUAL failure trigger)
- Existing fix PR (if found - include PR number and link)
- Recommendation (skip if fix PR already exists)
When not to use it
- →When the provided URL does not point to a GitHub Actions workflow run
Prerequisites
Limitations
- →Requires specific job-level history analysis rather than workflow-level summaries
- →Relies on the presence of identifiable error patterns like fatal or failing tags in logs
How it compares
Unlike manual log inspection, this tool automates the cross-referencing of job-specific run history and commit logs to verify failure patterns.
Compared to similar skills
gha side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gha (this skill) | 1 | 6mo | No flags | Intermediate |
| github-actions-failure-debugging | 1 | 7mo | No flags | Intermediate |
| github-actions-templates | 7 | 3mo | No flags | Intermediate |
| toolhive-release | 1 | 3mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ykdojo
View all by ykdojo →You might also like
github-actions-failure-debugging
Rabithua
Guide for debugging failing GitHub Actions workflows. Use this when asked to debug failing GitHub Actions workflows.
github-actions-templates
wshobson
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
toolhive-release
stacklok
Creates ToolHive release PRs by analyzing commits since the last release, categorizing changes, recommending semantic version bump type (major/minor/patch), and triggering the release workflow. Use when cutting a release, preparing a new version, checking what changed since last release, or when the user mentions "release", "version bump", or "cut a release".
ci-test-failures
dotnet
Guide for diagnosing and fixing CI test failures using the DownloadFailingJobLogs tool. Use this when asked to investigate GitHub Actions test failures, download failure logs, or debug CI issues.
ship
wilsonfaustino
Push current branch and create or update a GitHub PR with an intent-driven description. Use when the user says "ship", "ship it", "create PR", "push and PR", or wants to push their branch and open a pull request. Runs pre-flight safety checks, pushes to remote, and generates PR title/body from branc
upgrade-deps
obot-platform
Upgrade dependencies and runtimes safely, run CI, and report higher-risk options.