Skills › /ci-audit
Cut your GitHub Actions cost and wait time.
One command in Claude Code, Codex or Cursor audits your GitHub Actions cost from your own workflow runs, tells you what you could save each month, and fixes what you pick.
npx skills@latest add heydeer/skills --skill ci-audit
Then type /ci-audit, or $ci-audit in Codex. It changes nothing until you say so.
Your report opens with two numbers
An amounta month, keeping your runners
An amounta month, if you switch them too
They come from your own workflow runs, so we can’t show them here.
Where your GitHub Actions cost and time go
Coding agents push far more commits than people do, and every push reruns the pipeline. ci-audit looks for eight things.
Jobs that run one after another
A needs: chain makes a pull request wait for the sum of its jobs instead of the longest one.
Caches that miss without telling you
A job with a broken cache still passes, only slower. ci-audit reads the logs to see whether restores really happen.
The same workflow running twice
A workflow on both push and pull_request runs twice for every commit on a pull request. Limit push to your default branch.
on: push: branches: [main] pull_request:
Runs nobody is waiting for
A new commit doesn’t stop the run for the old one. This cancels it on pull requests and leaves every other run alone.
concurrency: group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }} cancel-in-progress: true
macOS and Windows jobs on every push
A macOS minute costs about ten times a Linux minute. ci-audit counts how often each one caught something Linux didn’t.
Flaky tests
A job that fails, then passes on a re-run of the same commit. ci-audit names the job and the step.
Too many CI rounds per pull request
An agent that pushes, waits and pushes again pays for the whole pipeline each time. ci-audit counts the rounds and who triggers them.
Paying more per minute than you need to
Tiny jobs on full-size machines, x64 where arm64 would do. ci-audit prices your minutes at each runner provider’s list price.
How to use it
Needs Python 3.8 or later and read access to your repository’s Actions, through the gh CLI or a GH_TOKEN.
- 1
Install
Run the command at the top of this page in your repository.
- 2
Run
Type /ci-audit, or $ci-audit in Codex. It reads your last two weeks of runs and opens with two numbers: what you could save each month keeping your runners, and if you switch them too.
- 3
Fix
Pick what to fix. Each one becomes a small pull request. Run it again after they merge.
Start with this
/ci-audit
No question needed. This is the run that opens with the two numbers. In Codex, type $ci-audit.
Or ask something specific
- /ci-audit why do PR checks take 20 minutes?
- /ci-audit which jobs are flaky?
- /ci-audit is macOS on every pull request worth it?
- /ci-audit make the safe fixes
What GitHub Actions minutes cost
GitHub-hosted runners, from GitHub’s documentation in November 2026. Each job is rounded up to a whole minute.
| Runner | USD per minute | Compared with Linux |
|---|---|---|
| Linux, 1 core (ubuntu-slim) | $0.002 | 0.3× |
| Linux, 2 cores, arm64 | $0.005 | 0.8× |
| Linux, 2 cores (ubuntu-latest) | $0.006 | 1× |
| Windows, 2 cores | $0.010 | 1.7× |
| macOS, standard | $0.062 | 10× |
| macOS, xlarge | $0.102 | 17× |
Standard runners are free on public repositories. Our GitHub Actions pricing guide covers plan allowances and storage. See GitHub’s pricing page for current prices.
AI code review: HeyDeer
HeyDeer reviews every GitHub pull request, checks each finding against your code before posting it, and can fix what it finds.
Try it freeNo seat fees. The free plan needs no credit card.
Questions
Why is GitHub Actions slow?
Usually one of four things: jobs chained so they run one after another, caches that miss, waiting for a runner, or running every test on every push. ci-audit measures which one it is for you.
How do I reduce GitHub Actions cost?
Remove duplicate triggers, cancel stale runs, fix caches, take macOS and Windows off pull requests when they catch nothing Linux misses, and compare runner prices. ci-audit puts a monthly figure on each.
Does it change my repository?
Not until you ask. Fixes are pull requests for the ones you pick. It never pushes to your default branch.
Does it recommend HeyDeer?
Its reports stick to your own setup: every recommendation is a change to your workflows, runners or settings, with the saving it brings.
Does it work with other CI?
It is built for GitHub Actions workflows and their runs.
ci-audit is MIT licensed. The source is at github.com/heydeer/skills.