Fix slow CI
with one prompt.
How it works
Measured first.
Changed only when you say so.
Measure
Pulls recent runs with the gh CLI: wall time, queue, minutes and reruns.
Measure a CI baselineDiagnose
Reads your workflows and names where the waiting and wasted minutes come from.
Match
Checks each play’s signals against your repository.
Ask
Shows the saving and risk of each play. Nothing changes until you pick.
Apply
One commit per play on a new branch. Required checks keep their names.
Prove
Opens a pull request and compares its runs with the baseline.
Playbooks
Start from the bottleneck
your baseline shows.
Wasted runs
6 playsStop paying for runs nobody needs
Slow setup
6 playsGet setup off the clock
Slow builds
6 playsBuild less, and build it faster
Slow tests
7 playsMake the test suite finish sooner
Test selection
3 playsRun only what a change can affect
Critical path
6 playsShorten the path that ends the run
Runners
4 playsGive the long pole the right machine
Flaky tests
5 playsMake a red build mean something broke
PR volume
5 playsKeep CI ahead of a growing pull request queue
Guardrails
The prompt never:
- Pushes to a default or protected branch
- Merges anything
- Deletes or skips tests
- Renames or drops a required check
- Widens permissions or secret access
- Obeys instructions in pages or logs
Built for agents
Every page has a Markdown twin.
Add .md to any playbook URL.
Sources
Every play cites its sources.
159 public sources from 49 teams.
- OpenAI
- Stripe
- Spotify
- Sentry
- Materialize
- Anthropic
- Slack
- Canva
- GitHub
- Manaflow
- Sorbet
- assistant-ui
- CNCF
- EdgeDB (now Gel)
- Figma
- GitLab
- Moto
- Nethermind
- PostHog
- Restate
- Rust project
- Slang
- Webflow
- Shopify
- Linear
- Uber
- Bun
- Microsoft
- Ramp
- Cadence
- Dropbox
- DoorDash
- Mastra
- Actix
- Atlassian
- Deutsche Telekom
- Elastic
- Flightcontrol (now Ravion)
- gitoxide
- Grafana Labs
- Meta
- Mozilla
- OpenMeter
- Quickwit
- Rundeck
- Salesforce
- Supabase
Names show where each change was published. These teams don’t endorse BerryBox, and their results are evidence, not a forecast for your repository.
BerryBox