mcpField
G
gha

gha

github.com/ykdojoCloud & DevOps10.3k85 installsUpdated 5w ago
Repository

About gha

gha is a skill for investigating GitHub Actions run URLs with the gh CLI. It focuses on identifying the actual failure trigger, checking job-specific history, and assessing possible fixes.

Key features

  1. 01Analyze workflow and job logs
  2. 02Check history for the failed job
  3. 03Assess recurring failures and success rate
  4. 04Verify a breaking commit
  5. 05Search open PRs for fixes

Use cases

  1. 01Find the cause behind an Actions run's exit code 1
  2. 02Determine whether a specific job failure is recurring
  3. 03Identify a commit linked to a persistent regression
  4. 04Check whether an open PR may already fix a failure

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ykdojo/claude-code-tips --skill gha

After installing, type/ghain Claude Code to confirm it loaded.

Details

From the project README

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

  2. 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?

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

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

  5. 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)

Comments

Markdown supported