// "Fix GitHub Actions CI failures using GitHub CLI (gh): inspect runs/logs, identify root cause, patch workflows/code, rerun jobs, and summarize verification."
| name | ci-fix |
| description | Fix GitHub Actions CI failures using GitHub CLI (gh): inspect runs/logs, identify root cause, patch workflows/code, rerun jobs, and summarize verification. |
gh to locate failing runs, inspect logs/artifacts, rerun jobs, and confirm the fix.OWNER/REPO) and whether this is a PR or branch build.gh context
gh auth statusgh repo view --json nameWithOwner -q .nameWithOwner-R OWNER/REPO to all commands..../actions/runs/<id>.gh run list --limit 20 --status failuregh run list --branch <branch> --limit 20 --status failuregh run list -w <workflow> --limit 20 --status failuregh run view <id> --webgh run view <id> --verbosegh run view <id> --log-failedgh run view <id> --log --job <job-id>gh run download <id> -D .artifacts/<id>references/ci-failure-playbook.md for common patterns and safe fixes..github/workflows/*.yml.gh run rerun <id> --failedgh run view <id> --json jobs --jq '.jobs[] | {name,databaseId,conclusion}'gh run watch <id> --compact --exit-statusgh workflow run <workflow> --ref <branch>pull_request_target (and any change that runs untrusted fork code with secrets) unless the user explicitly requests it and understands the security tradeoffs.permissions: least-privilege; don’t broaden token access “just to make it pass”.