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.

referencespatternsopt12-duplicated-setup-across-jobs.md

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

OPT12 — Duplicated Setup Across Jobs

TL;DR: Several jobs copy-paste the same setup steps, or repeat the same test suite before later work can run. A shared action only reduces maintenance; handing duplicate test work to the existing gate removes one suite run while preserving every check.

Anti-pattern: Multiple jobs with identical preamble steps (checkout, setup-node, pnpm install, build) that could be extracted to a composite action or use artifact handoff.

Detection heuristic:

# Hash the first N steps of each job and compare
# Look for identical sequences of: checkout → setup-pnpm → setup-node → install → build

Fix: Extract shared setup into a composite action, or build once and pass artifacts to downstream jobs.

Duplicate test work on one lane

When two jobs on the same trigger and concrete runner platform execute the same test command, and one copy sits on a later job's needs: chain, keep every gate and execute the suite once. Within one workflow, make the later job depend on the existing test job. Across workflows, trigger the consumer with workflow_run and check the producer workflow's conclusion before continuing. If the second run exists only to collect coverage, move that coverage floor onto the existing test run.

Expand local composite actions before comparing commands. Matrix legs on different operating systems or architectures are platform coverage and are not duplicates. Removing a test job or weakening a required status is never the fix.

Runner minutes fall by one measured suite run per execution. The cross-workflow handoff waits for the producer workflow to complete, so its wall-clock credit is max(0, duplicate job duration - producer workflow completion after push). A same-workflow needs: handoff receives zero wall-clock credit. Measure both axes from sampled runs.

GUARDRAIL — "downstream ignores producer's artifact" claims (REQUIRED before any cross-workflow handoff finding):

If your finding crosses workflow boundaries and frames the fix as "consumer ignores producer's artifact", "wire up the [producer] artifact", or "downstream throws away the [producer] output", you MUST grep -nE 'actions/upload-artifact' the producer workflow file BEFORE accepting the framing. Two valid outcomes:

  1. Producer DOES upload an artifact → finding is valid as written. Cite the upload step's file:line in evidence. Fix is "add actions/download-artifact in the consumer".
  2. Producer does NOT upload an artifact → reframe the finding. The producer's "output" is whatever it actually publishes — most commonly a warm Turbo / build-tool remote cache (check for TURBO_CACHE: remote:rw, sccache, ccache, nx affected, etc.) or a PR status update. The fix is then "ADD actions/upload-artifact to the producer AND add actions/download-artifact to the consumer" — that is a NEW pipeline design, not a re-wiring. Re-size the savings: the redundancy is pnpm install / cargo fetch / equivalent install-step cost only, NOT "downstream rebuilds the full monorepo from scratch". Use measured P50/P95 of the build step to size the cold-tail recovery component; never assume 100% cold.

Severity cap. A finding that survives outcome (2) — i.e. the producer doesn't upload — is capped at HIGH severity, never CRITICAL, because the saving is bounded by install dedup + measured cold-tail, not by full rebuild elimination.

Required evidence text: include one of these two literal lines:

  • Verified <producer-workflow> uploads <artifact-name> at L<N>; consumer <consumer-workflow> does NOT call actions/download-artifact. Wiring fix applies.
  • Verified <producer-workflow> does NOT upload any artifact (no actions/upload-artifact step). Producer's output is <warm-cache | PR-status | other>. Fix is a NEW pipeline; saving re-sized to <X> min/mo from measured install + cold-tail, NOT 'downstream rebuilds from scratch'.

A prebuild-dedupe audit that assumed "downstream rebuilds from scratch" when the producer never actually uploaded an artifact is the empirical motivation for this guardrail — verify the upload before sizing.


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