Inspect workflow and job timings and billable minutes through the GitHub API with optimise-github-actions, born from real team usage challenges.
optimise-github-actions
Optimise GitHub Actions for cost and speed. Reads the billed minutes and wall-clock time of every workflow and job from the GitHub API, finds the waste, and changes the workflows without dropping the checks that matter. Typical waste is main re-running suites the pull request already passed, path filters that match every PR, small matrix jobs, missing caches, draft pushes, Docker builds, Windows and macOS multipliers, hung jobs and bots. Use this whenever the user says CI is slow or expensive, is over their Actions quota or paying overage, wants to "reduce GitHub Actions minutes", "speed up CI" or "make CI cheaper", asks "why is our CI so expensive", or wants a CI audit. Use it even if they only point at one slow job or one workflow file.
ソース情報
- リポジトリ
- enesgules/dotfiles
- ソースの最終更新活動
- 2026年9月29日 14:02
- 検出された SKILL.md の言語
- 英語
- スター
- 25
- フォーク
- 1
optimise-github-actions: Find wasted CI time and
Measure GitHub Actions workflow and job usage through the GitHub API, then identify duplicate runs, ineffective path filters, setup overhead, cache gaps
Prerequisites
The measurement script needs Node.js and gh with read access to the repository. The workflow also inspects rulesets, branch protection and deployment dependencies before proposing edits.
How to use
Run the source’s measurement command with your repository substituted for OWNER/REPO:
node <skill-dir>/scripts/measure.mjs OWNER/REPO --days 14 --out jobs.json
Use the resulting workflow/job tables and raw rows to rank waste. Review the estimated minutes, elapsed time and risk before selecting changes; validate edited workflows with actionlint and the repository’s CI tests.
Limitations
Cost and speed can move in opposite directions when jobs are split or merged. Savings that depend on team behavior remain unmeasured until supported by data. Do not remove or rename required checks without inspecting protection rules. Moving work to self-hosted runners requires the operator to confirm capacity, architecture and access.
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SKILL.md を表示中
| name | optimise-github-actions |
|---|---|
| description | Optimise GitHub Actions for cost and speed. Reads the billed minutes and wall-clock time of every workflow and job from the GitHub API, finds the waste, and changes the workflows without dropping the checks that matter. Typical waste is main re-running suites the pull request already passed, path filters that match every PR, small matrix jobs, missing caches, draft pushes, Docker builds, Windows and macOS multipliers, hung jobs and bots. Use this whenever the user says CI is slow or expensive, is over their Actions quota or paying overage, wants to "reduce GitHub Actions minutes", "speed up CI" or "make CI cheaper", asks "why is our CI so expensive", or wants a CI audit. Use it even if they only point at one slow job or one workflow file. |