Fix CI
DevOps & Securityfix-ciFix CI is an Agent Skill for devops & security published in the ccusage/ccusage repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Diagnoses and fixes failing GitHub Actions checks with gh. Use when CI fails on a pull request and needs logs, focused fixes, and validation.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/ccusage/ccusage/blob/HEAD/.agents/skills/fix-ci/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/fix-ci, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Fix CI
Use this when a PR check fails or the user asks to fix CI. This skill is repo-local so contributors can follow the same workflow without relying on a personal global skill.
Workflow
-
Inspect PR checks:
gh pr checks gh pr view --json url,headRefName,statusCheckRollup -
Identify failed GitHub Actions runs and jobs. Ignore pending checks until they finish unless the failure is already clear.
-
Fetch failed logs:
gh run view <run-id> --log-failed gh run view <run-id> --json jobs -
Fix the smallest cause that explains the failed check. Use the relevant repo skill or nearest package guidance for the area being changed, such as
testing,development, ordocs/AGENTS.md. -
Validate locally with the narrowest command that reproduces the failure, then run the relevant broader checks. Let git hooks run normally.
-
Commit the fix as a small independently revertible commit using the
commitskill. If the fix requires a manifest or lockfile update, include both in the same commit. -
Push normally and use
create-prto comment or request another review pass when appropriate.
Notes
- Prefer
ghover browser-only inspection so logs and job IDs are reproducible. - Do not mix unrelated review cleanups into a CI fix commit.
- If CI failed because of generated output or formatting, commit only the generated/formatting result that the failing check requires.