SkillsAdd

smithery.ai

gha

Analyze GitHub Actions failures and identify root causes

First seen Mar 26, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,556 B
  • docs SUMMARY.md 67 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Investigate this GitHub Actions URL: $ARGUMENTS

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

  1. 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

  1. 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, then gh run view <run-id> --json jobs to 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?

  1. 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

  1. 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

  1. 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

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)