Fix slow GitHub Actionswith /ci-speedup
Install the agent skill to diagnose what’s slowing down CI on your PRs and fix it.
Open source, MIT licensed. Runs on your machine.
What ci-speedup does
- Deterministic core
- Detection, ranking, critical-path analysis, and every measured number are reproducible.
- LLM boundary
- Only unmatched blocking logs get a grounded LLM read. Your coding agent uses the evidence and repository context to draft the fix.
One required check often sets how long every PR waits to merge. ci-speedup samples your real Actions runs, finds that blocking check, and gives your coding agent the evidence to shorten it safely.
Reads your workflows and code
It opens your GitHub Actions workflow files and the code they build and test, so it understands what your CI is supposed to do and where the time should be going.
Analyzes your real runs and logs
Through your own GitHub CLI it pulls your recent Actions runs, job timings, and logs. Real numbers from your repo, on your machine. Nothing is sent to StarSling.
Finds the bottleneck
It works out which checks actually block a PR from merging and which one sets the total wait, then digs into that check step by step for the root cause.
Prompts your agent to fix it
Every finding ends in a ready-to-paste prompt carrying the root cause, the log evidence, and the measured cost. Your coding agent checks the code and its git history first, so the fix is safe and intended, then writes the change for you to review.
Seventy-three patterns, one measured spine.
The catalog catches hygiene and structural issues, but the report elevates only evidence-backed causes.
Shard tests across parallel jobs
The full fix for OPT24: good/bad YAML, a verify checklist, and a copyable fix prompt.
in-depth guide / OPT28Use a shallow checkout with fetch-depth
The full fix for OPT28: when to use depth 1 vs 2 vs 0, with copyable YAML.
guide hubAll GitHub Actions best practices
Every guide in the catalog’s authority layer, on this site.
Real fixes ci-speedup has shipped in production
Instead of hand-fixing from a list of 73 guides, ci-speedup measures which pattern applies to the check that is actually blocking your PR.
- Read the Mastra customer storyMerged 2026-04-29
Customer storyci: shard E2E kitchen-sink across 3 parallel jobs
StarSling split Mastra's E2E kitchen-sink workflow across a shard matrix and passed the shard number into Playwright.
Read the Mastra customer storyView PR #15888 in mastra-ai/mastra (opens in new tab) - Read the Better Auth customer storyMerged 2026-02-13
Customer storychore: fix turbo cache configuration in ci
StarSling found that setting TURBO_CACHE to remote:rw disabled Turborepo's local cache, so .turbo was never written and the actions/cache save step had nothing to store; removing the override restored the local-plus-remote default so the build cache persists across runs.
Read the Better Auth customer storyView PR #7950 in better-auth/better-auth (opens in new tab)
Questions about ci-speedup.
What is ci-speedup?
ci-speedup is a free, open-source agent skill that analyzes your GitHub Actions workflows and recent runs, finds the merge-gating checks that set PR wait time, ranks their long poles, and produces an evidence-backed prompt for your coding agent to draft the targeted fix.
Is ci-speedup free?
Yes. ci-speedup is free, open source, and MIT licensed. You can install it from the public StarSling skills repository and run it in your own repository.
Does ci-speedup send my code to StarSling?
No. ci-speedup runs locally through your coding agent and uses your authenticated gh CLI to read GitHub Actions runs, timings, and logs. It does not send your code or CI data to StarSling.
How does ci-speedup find what's slowing my GitHub Actions down?
It deterministically identifies the required checks on the blocking path, measures recent job and step timings, and runs registered detectors from a 73-pattern CI optimization catalog. It explains evidence-backed causes and reports detector gaps honestly; your coding agent uses the repository context to draft the fix.
Which coding agents does ci-speedup work with?
ci-speedup works with all 73 coding agents currently supported by Vercel's Skills CLI, including OpenCode, Claude Code, Codex, and Cursor.
Optimize your GitHub Actions using your own AI agents.
/ci-speedup finds the required checks gating your merges, ranks their long poles, then hands your agent the evidence-backed prompt: shard it, cache it, shorten the checkout. Wall-clock time per PR drops, and you review the diff before it merges.
Don’t want to run it each time? On paid plans, once optimization PRs are enabled, StarSling does this automatically, keeping the long pole short as your workflows change.
Get StarSlingGet the StarSling app