Help us improve
Share bugs, ideas, or general feedback.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dx:gha <url><url>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Investigate this GitHub Actions URL: $ARGUMENTS
Inspects GitHub Actions workflow runs using gh CLI: lists runs, checks status, analyzes logs, debugs failures, reruns jobs. Use for CI/CD troubleshooting.
Monitors GitHub Actions workflow runs, identifies failing jobs, extracts error logs, and summarizes diagnostics. Useful for checking CI status after pushes or investigating failures.
Diagnoses and fixes GitHub Actions CI failures in pull requests by fetching job logs, identifying root causes like build or test errors, and proposing targeted code changes.
Share bugs, ideas, or general feedback.
Investigate this GitHub Actions URL: $ARGUMENTS
Use the gh CLI to analyze this workflow run. Your investigation should:
Get basic info & identify actual failure:
Check flakiness: Check the past 10-20 runs of THE EXACT SAME failing job:
gh run list --workflow=<workflow-name> to get run IDs, then gh run view <run-id> --json jobs to check the specific job's statusIdentify breaking commit (if there's a pattern of failures for the specific job):
Root cause: Based on logs, history, and any breaking commit, what's the likely cause?
Check for existing fix PRs: Search for open PRs that might already address this issue:
gh pr list --state open --search "<keywords>" with relevant error messages or file namesWrite a final report with: