Fix CI
Find the first actionable failure in a PR's CI checks, apply the smallest safe fix, and loop until all checks are green.
Fix CI
A PR's CI is red. Don't guess — read the checks, find the first actionable error, fix it, push, and repeat.
When to use
- A branch or PR has failing CI checks.
- CI output is ambiguous and needs systematic triage.
How to apply
- Run
gh pr checks --json name,bucket,state,workflow,linkto get the full check set. - Find the first failed job. Use GitHub Actions logs when available; otherwise follow the check link to identify the failing command.
- Extract the first actionable error — one thing, not everything.
- Apply the smallest safe fix.
- Push, re-run
gh pr checks, repeat until green.
Fix one failure at a time. Prefer minimal, low-risk changes before broader refactors. gh pr checks is the source of truth — don't assume a fix worked until it shows green there.
Output should feel like
- Primary failing job and root error stated up front.
- Fixes listed in the order they were applied.
- Final CI status confirmed from
gh pr checks.
Related
- fix-merge-conflicts — resolve the conflicts that often precede CI failures.
- git-conventions — commit format for the fix commits.
- skills-index — vault catalog.
linked from3
- Fix Merge ConflictsResolve merge conflicts non-interactively with correctness-first edits, validate the build, and summarize resolution decisions.
- Git ConventionsConventional commit format and branch naming rules used as a reference when writing commit messages or advising on version control practices.
- AI SkillsReusable operating manuals for LLM agents.