Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis.
98
Does it follow best practices?
Validation for skill structure
Diagnose CI failures and implement fixes with minimal, targeted diffs. Pushes fixes to a dedicated branch without creating PRs.
Verify GitHub CLI authentication before proceeding:
gh auth statusIf not authenticated, instruct the user to run gh auth login first.
Determine the failing workflow run. If working on a PR branch:
gh pr view --json statusCheckRollup --jq '.statusCheckRollup[] | select(.conclusion == "FAILURE")'If working from a branch or run ID:
gh run list --branch <branch> --status failure --limit 5
gh run view <run-id> --verbosePull logs from failed steps to identify the root cause:
gh run view <run-id> --log-failedFor deeper inspection:
gh run view <run-id> --log --job <job-id>
gh run download <run-id> -D .artifacts/<run-id>Analyze logs for common failure patterns:
Prefer the smallest fix that resolves the issue. Deterministic code fixes are better than workflow plumbing changes.
Make minimal, scoped changes matching the repository's existing style:
Create or update a dedicated fix branch:
git checkout -b ci-fix/<original-branch>
git add -A
git commit -m "fix: resolve CI failure in <job-name>
Co-Authored-By: Warp <agent@warp.dev>"
git push -u origin ci-fix/<original-branch>If the fix branch already exists, update it:
git checkout ci-fix/<original-branch>
git pull origin <original-branch>
# make fixes
git commit -m "fix: <description>
Co-Authored-By: Warp <agent@warp.dev>"
git pushTrigger CI on the fix branch and monitor:
gh run list --branch ci-fix/<original-branch> --limit 1
gh run watch <new-run-id> --exit-statusTo rerun only failed jobs:
gh run rerun <run-id> --failedpull_request_target unless explicitly requested—it can expose secrets to untrusted codepermissions: minimal; don't broaden access to make tests passAfter fixing, provide a brief summary:
2ca570e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.