Fix CI
-
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.


