Index of every page on this site: llms.txt
All skills
Run it yourself

Audits a repository's GitHub Actions workflows for CI optimization opportunities — missing caches, redundant setup, sleep-based readiness, long test jobs without sharding, full-history checkout, dead env vars, build-cache misconfig, and ~60 more patterns across caching, redundancy, parallelization, conditional execution, trigger scope, and hidden failures. Use when: (1) analyzing a repo's CI for optimization opportunities, (2) producing a prioritized report with measured wall-clock and runner-minute savings, (3) re-auditing after upstream CI changes. Do not trigger for: general CI setup help, writing new workflows from scratch, non-GitHub-Actions CI systems, or security/posture audits — use `ci-secure` for those.

Use this Skill: https://skilld.dev/gh/starslingdev/skills/ci-speedup

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencespatternsopt107-batch-default-branch-full-ci.md

≈767 tokens on demand. Your agent reads this file only when SKILL.md points to it.

OPT107 — Default-Branch Full CI Runs Too Often to Stay Current

TL;DR: A busy default branch starts the full post-merge suite for every merge even when another merge replaces that commit before, or shortly after, the run finishes. Keep the pull-request gate unchanged and validate the current default-branch tip on an hourly schedule instead, with a repository variable that can restore per-push validation immediately.

Detection heuristic: inspect measured push runs on the repository's default branch. A run is batchable when a later default-branch push starts before it finishes or within one hour afterward. Report only when at least two runs and at least 25% of the readable sample are batchable, and when at least three completed push runs provide job timing. Within each dense cluster, reserve the most conservative number of hourly replacement validations, then credit only removable runs whose own completed-job compute is readable. A truncated run page is a lower bound, never extrapolated into unreadable or unseen runs. Sparse pushes and release-, deploy-, publish-, or migration-like workflows stay quiet.

Fix recipe (safest first):

  1. Keep every pull-request check and required gate unchanged.
  2. Add an hourly schedule (and retain workflow_dispatch) that checks out and validates the current default-branch tip.
  3. Put the per-push versus scheduled mode behind a repository variable so an owner can switch back without reverting workflow code.
  4. Keep deploys, releases, migrations, cache publication, and other commit-specific side effects on their existing event. Only batch repeatable validation whose result is meaningful for the current tip.

Sizing: runner-minute effect is a saving (negative usage): the sum of each credited removable run's own completed-job compute, after reserving conservative hourly replacement slots. Jobs with commit-specific side effects (a deployment environment, a deploy/release/publish name, or a publish, push, deploy or migration step) stay on their push event and are left out of that compute. Developer merge wait is unchanged because the pull-request gate stays unchanged. The report states the signed runner-minute effect for the fetched sample window, and a monthly estimate when the workflow's 30-day default-branch push-run count is readable: the sample saving times that count over the sampled push runs, capped at the workflow's measured 30-day validation compute, labelled as an estimate from the sampled runs. When the 30-day count is unreadable the monthly saving is reported as unsized, with the reason.

Public example: OpenClaw pull request 156783 batches full default-branch validation while preserving pull-request coverage.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    The skill is a robust CI optimization tool that audits GitHub Actions workflows. It identifies performance bottlenecks using deterministic logic and provides analysis of job logs. While it processes untrusted log data, it includes strong defensive instructions to mitigate indirect prompt injection. A minor best-practice issue regarding unsafe YAML loading was identified in a utility script.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: CRITICAL · 2 issues

Signed by skilld at 9a84115. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 16 hours ago.

Activeupdated yesterday

README badge

README badge for starslingdev/skills/ci-speedup