ci-speedup
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 hel
Profile →npx skills add starslingdev/skills --skill ci-speedup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Audits a repository's GitHub Actions workflows against a 73-pattern catalog (67 hygiene/data-driven patterns plus 6 structural/critical-path patterns) to identify CI optimization opportunities such as missing caches, redundant setup, long-running tests, and other inefficiencies. It produces a root-cause-analysis report that shows measured impact on two axes: developer wall-clock wait and runner-minutes, and it includes aLong-poles section and a Findings section with prioritized observations. It does not prescribe fixes; instead, it provides a ready-to-paste agent prompt for each finding along with measured costs.
How it works
- The audit runs via a structured process using scripts and data; static scanning is performed by
scripts/scan.pywhich parsesreferences/optimization-patterns.mdand applies detectors to the repository, producing findings JSON and a coverage listcatalog_patterns_without_detector. - A data-pass is added by
scripts/collect_runs.pyusing run-history data to compute two-axis sizing (e.g., p50/p95/mean) and a critical-path model; this is orchestrated byrun.pywith flags like--root,--out,--repo, and--with-logsto fetch logs and generate adata_bundlealongside<OUT>.json. - The render stage is performed by
scripts/blocking_path.py --in findings.json, which outputs a report containing a Bottom line, a Contents TOC of gates, per-pole drill-downs, and a ready-to-paste agent prompt. If there is a gap-fill scenario for logs that match no detector, the agent produces a dedicated LLM gap-fill analysis and renders it with--analysisbindings.
When to use it
Use when analyzing a repository's CI for optimization opportunities, when producing a prioritized report with measured wall-clock and runner-minute savings, or when re-auditing after upstream CI changes. Do not trigger for general CI setup help, writing new workflows, non-GitHub-Actions CI systems, or security/posture audits.
What it can touch
- The workflow detection, data gathering, and reporting pipeline rely on tools and scripts named in the process:
scripts/scan.py,scripts/collect_runs.py,run.py,scripts/blocking_path.py, andreferences/optimization-patterns.mdfor detectors. The phase usesghCLI authenticated access andpython3with PyYAML (pip install pyyaml). The output includesfindings.json, a data bundle under<OUT>.data, and a generatedci-speedup-findings-report.mdwhen saved.
Caveats
- The tool does not prescribe fixes; it only reports findings with measured impact and provides a tailored agent prompt for remediation. Structural findings include mandatory risk, guardrail, and rollout in their prompts. If a drilled pole has no detector match, it results in a manual-review appendix rather than a finding. Requires an authenticated gh CLI for data pass; without authentication, phase 1 gates out to static-pattern scanning only.
# ci-speedup — CI Optimization Audit for GitHub Actions Audits a repository's GitHub Actions workflows against a 73-pattern catalog — 67 **hygiene/data-driven** patterns plus 6 **structural / critical-path** patterns routed from the measured long pole — and produces a **root-cause-analysis** report with measured impact on two axes — developer wall-clock wait and runner-minutes (cloud bill). The re
What does the ci-speedup skill do?
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 hel
How do I install it?
Run `npx skills add starslingdev/skills --skill ci-speedup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From starslingdev/skills, a repository with 11 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.