fix-ci
Installation
SKILL.md
Fix CI
A red check is routing evidence, not ownership. Find the causal owner before changing code.
1. Freeze the failure
- Read the repository instructions and inspect the current worktree, branch, dirty state, active PR, target branch, and stack.
- Run the CI provider's cheapest auth and connectivity preflight. For GitHub, use
gh auth statusplus one read-only API probe. Treat keyring, sandbox, DNS, connectivity, and provider5xxfailures as environment failures; refresh credentials only after a host-capable request returns a confirmed authentication rejection. - Snapshot the live PR head, base, state, mergeability, checks, and review state before mutation.
- Read the failing job's annotations and logs. Record the exact workflow, job, run URL, head SHA, failure text, and first actionable frame. Inspect external-provider checks through their own evidence surface when available; otherwise retain their URL and mark the missing evidence.
This step is complete when every red required check is accounted for and its evidence is tied to an exact SHA. A check name or red badge alone is not a diagnosis.
2. Prove the causal owner
Compare the failing head with the PR diff, its merge result, the target branch, recent target-branch runs, and any existing repair PR. Classify each failure as exactly one: