Rank fixes by the minutes they save

Price every CI fix in minutes saved per day before writing any YAML.

Prompt

Evaluate and apply this CI technique to my repository: Rank fixes by the minutes they save.

Price every CI fix in minutes saved per day before writing any YAML.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/rank-by-minutes.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How OpenAI used this technique

Read what OpenAI changed and follow the original sources.

Rank fixes by the minutes they save

The team asked its agent to read the repository's CI run history, list ideas to relieve CI load, and rank them by estimated CI minutes saved per day. Following up on that ranked list produced about 30 CI optimization PRs.

About 30 CI optimization PRs landed after ranking ideas by CI minutes saved. Source

Use it when: You have CI run history and want to choose a first optimization.
Before applying it: Estimates depend on the history window and run frequency. Rank total CI minutes separately from time waiting for a merge.

How OpenAI used this technique

Rank fixes by the minutes they save

Company Playbooks

Related guides

Make GitHub Actions faster