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.

referencespatterns_frame.md

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

<!-- Non-pattern text of the compiled ../optimization-patterns.md: the preamble (with the Contents section and its category blurbs) and each `## Category N:` heading block, placed before the first pattern of that category. Each section runs from its marker line to the next marker. Edit here, then run build_catalog.py. --> <!-- frame: preamble -->

ci-speedup Pattern Catalog

This catalog defines every CI optimization pattern the ci-speedup skill can detect. Each entry has a single METADATA block followed by the pattern's anti-pattern, detection heuristic, and fix recipe.

Catalog scope. Patterns are organized into 14 categories (Caching, Redundancy, Docker, Parallelization, Actions and Checkout, Conditional Execution, Trigger and Scope, Release Workflow, Queue Times and Concurrency, Timing Anomalies, Stack-Specific, Build Caching, Hidden Failures and Dead Config). Each pattern carries an impact tier (HIGH/MEDIUM/LOW) and a detector field naming the scanning strategy used. The scanner consumes the METADATA blocks directly — adding a new pattern is a matter of writing its catalog entry and (for novel detector types) extending the scanner.

OPT-id assignment rule. Each OPT<n> id is permanent and never reused, even after a pattern is cut — a cut pattern's id stays retired so historical reports, evals, and fix-strategy strings never collide with a different pattern. Assign a new id to every new pattern (the next unused number; there are gaps from retired/never-assigned ids, e.g. 10, 67). Do not renumber existing patterns. fix_strategy slugs and the _SIZING keys are keyed on these ids, so reuse would silently mis-size or mis-link old data.

Contents

Patterns are ### OPT<n> — Title blocks grouped into categories. This file is large; navigate by grep — OPT33, ## Category 7, or a keyword like turbo / concurrency jumps straight to the entry. The categories (grep ## Category N):

  1. Caching · 2. Redundancy · 3. Docker · 4. Parallelization · 5. Actions and Checkout · 6. Conditional Execution · 7. Trigger and Scope · 8. Release Workflow ·
  2. Queue Times and Concurrency · 10. Timing Anomalies · 11. Stack-Specific ·
  3. Build Caching (Language-Agnostic) · 13. Hidden Failures and Dead Config ·
  4. Structural / Critical-Path Levers
  • Category 1 — Caching (OPT1–): tool installs, build/test caches, dynamic cache keys, and the one pattern pointed the other way — a cache measured to cost more than it saves (OPT79), NuGet restores placed on a slower Windows disk (OPT93), caches never saved on the default branch (OPT96), cache paths that never exist at save time (OPT101).
  • Category 2 — Redundancy: duplicate env, repeated setup sequences, redundant build steps, repeated fixed setup across independent small jobs (OPT77).
  • Category 3 — Docker: sleep-based readiness, over-broad compose up.
  • Category 4 — Parallelization: needless needs: serialization, unsharded long jobs, a test worker count nobody measured (OPT88), the slowest platform compiling its own tests (OPT89).
  • Category 5 — Actions and Checkout: stale action pins, repeated setup, full-history checkout, submodule / Git LFS checkout payload, checkout stalls on the tail (OPT80).
  • Category 6 — Conditional Execution: merge_group step-vs-job conditions, draft-PR gating.
  • Category 7 — Trigger and Scope: missing path filters, no --filter on PR turbo, cron frequency, every PR paying for coverage that could run after merge (OPT90).
  • Category 8 — Release Workflow: release-path caching + redundancy.
  • Category 9 — Queue Times and Concurrency: missing/!coarse concurrency groups; measured one-at-a-time capacity waits (OPT97) and repeated merge validation (OPT98).
  • Category 10 — Timing Anomalies: failure-rate / bimodal duration signals (advisory), and the same job measured faster on another runner class (OPT81), and infrastructure faults that fail whole runs (OPT100).
  • Category 11 — Stack-Specific: turbo task outputs, unstable turbo env keys, type-aware ESLint on a slow lint job (OPT82), Lighthouse CI audits multiplied by runs, URLs and device passes (OPT103).
  • Category 12 — Build Caching (language-agnostic): uncached compiled-language builds, a dependency compiled from source when a prebuilt package exists (OPT86), a compile nobody profiled (OPT91), a machine-wide .NET SDK reconciling unrelated workloads (OPT94).
  • Category 13 — Hidden Failures and Dead Config: dead env vars, misconfigured caches.
  • Category 14 — Structural / Critical-Path Levers (OPT70–OPT75, OPT78, OPT83–OPT85, OPT87): routed from the measured long pole (see ARCHITECTURE §11), not a flat grep. OPT87 and OPT74 remain manual. OPT78 and OPT85 are routed by drill-time log leaves; OPT83 and OPT84 are routed by structural passes over the drilled poles' step decomposition plus the workflow YAML, not by the log leaves (OPT84 also follows the step's package.json scripts).

(Catalog OPT-ids are the static scan; the blocking_path.py _parse_log leaf detectors — prisma / vitest / turbo / playwright — are a separate set run over the drilled long poles' captured logs, documented in ARCHITECTURE §12.3. OPT78 is the one catalog entry routed by that log-leaf set: it documents and reserves the id for the vitest-isolate-pool leaf, and is not part of the static scan.)


<!-- frame: category 3 -->

Category 3: Docker


<!-- frame: category 4 -->

Category 4: Parallelization


<!-- frame: category 5 -->

Category 5: Actions and Checkout


<!-- frame: category 7 -->

Category 7: Trigger and Scope


<!-- frame: category 8 -->

Category 8: Release Workflow


<!-- frame: category 10 -->

Category 10: Timing Anomalies


<!-- frame: category 11 -->

Category 11: Stack-Specific

The patterns below apply only when the repo uses the listed tools. Skip the entire category if the repo's stack doesn't match.


<!-- frame: category 12 -->

Category 12: Build Caching (Language-Agnostic)


<!-- frame: category 14 -->

Category 14: Structural / Critical-Path Levers

These patterns are a different class from everything above. The catalog patterns OPT1–OPT69, OPT76, OPT77, OPT79, OPT80, OPT81, OPT82, OPT86, OPT88–OPT91, OPT93, OPT94, OPT96, OPT97, OPT98, OPT100, OPT101 and OPT103 are hygiene: each is a named, locally-checkable defect with a mechanical, low-risk fix, detected by matching workflow YAML against the catalog. OPT81, like OPT79 and OPT80, is derived from run history rather than matched against YAML, and its A2 advisory is risk MEDIUM. On real repos almost every hygiene hit moves ~0 developer wall-clock — the true bottleneck is usually a check that is working as intended but is simply the slowest thing on the critical path, with no catalog match.

Structural patterns attack exactly that gap. They are not detected by declarative YAML matching; they are routed from the measured critical path (collect_runs.py decomposes the long-pole job, cross-references required checks, and finds shared/redundant work), and the final lever framing is written by a per-candidate reasoning step. They carry an OPT-id so the report and tests stay catalog-keyed, but the catalog is no longer the only thing that can produce a finding.

Most of them (OPT70–OPT75) are routed by the deterministic structural router in collect_runs.py. OPT83 and OPT84 are each routed by a structural pass over each drilled pole's per-step decomposition and its workflow YAML (not by the log leaves) and emit a finding with its own card; OPT84 also reads the repo's package.json scripts and tool versions. OPT87 and OPT74 remain listed as structural patterns without a detector. OPT78 and OPT85 are routed instead by drill-time leaf detectors over the long pole's captured log (ARCHITECTURE §12.3), corroborated against the repo's test-runner config. It emits no finding record, so the render boundary's Risk row and banner never see it: its HIGH risk is stamped on the pole's drill-down and its intent check, guardrail and rollout ride in its agent prompt. scan.py reports it as having no critical-path router so its coverage is never overstated.

The cost of the higher leverage is higher risk. A hygiene fix at worst does nothing. A structural change can degrade correctness — drop coverage, turn a real failure into a false green, diverge from the shipped artifact. So every structural pattern declares a risk rating, a mandatory guardrail, and a conservative rollout in its METADATA, and the report ranks on savings AND risk as separate axes: a high-savings/high-risk candidate can sit below a boring safe one. A structural finding is NEVER presented as a safe quick win.

risk values: LOW (mechanical, reversible, no correctness exposure) < MEDIUM (changes a signal/trigger; reversible but can drop a check developers rely on) < HIGH (can silently change what is built/tested/shipped — correctness exposure). The report's ranking demotes by risk so the rule is visible and a future edit can't quietly re-promote a HIGH-risk lever into the quick-wins list.

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