Fix CI
SkillMonitoring & opsWhen a pull request fails its GitHub Actions checks, this skill lets your AI work out why and fix it. It reads the failure logs, makes focused changes, and validates the fix by testing locally. The result is failing checks that get resolved instead of stalling your pull request.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding it, point your AI at a pull request whose checks are failing and ask it to fix the CI. It will pull the logs, make a focused fix, and test it locally.
Then ask your AI: use the Fix CI skill
What your AI can do with it
- Diagnose why GitHub Actions checks are failing on a pull request
- Read the failure logs to pinpoint the cause
- Make focused fixes to the code that broke the checks
- Validate fixes with local testing
What this skill tells your AI
The instructions your AI receives, as published by ccusage/ccusage in .agents/skills/fix-ci/SKILL.md and read by ahel’s review.
-
Read the check state with
gh pr checks, then pull the failing job logs withgh run view <run-id> --log-failed. Logs fetched throughghare reproducible; browser-only inspection is not. Pending checks can usually wait unless the failure is already clear. -
Reproduce locally. CI runs almost everything through Nix, so the failing step maps onto a
justrecipe:CI job / step Local preflight, orRun nix flake checkjust checkRun Rust tests(nix build .#ccusage-tests)just rust::testJS testjust test-nodeBabashka performance harness testapps/ccusage/scripts/compare-pr-performance_test.cljStart with the narrowest command that reproduces the failure — a single
cargo testfilter — before the recipe above. -
Fix the smallest cause that explains the failed check, using the skill for the area being changed:
testing,development,docs, or the nearest packageAGENTS.md. When the failure was generated output or formatting, commit the regenerated result the check requires rather than hand-editing it. -
Commit with the
commitskill; a manifest change and its lockfile update belong in the same commit, and unrelated cleanups belong in separate ones. Let the git hooks run. -
Push, then use
create-prto comment or request another review pass when appropriate.
Signals
- GitHub stars
- 18k
- Forks
- 821
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
fix-ci-ccusage- Source
- github.com/ccusage/ccusage