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.

referencespatternsopt114-docker-npm-audit.md

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

OPT114 — Docker Image Layers Repeat npm Advisory Lookups Already Run by CI

Anti-pattern: A CI job runs npm ci on the host with npm's default audit reporting, then builds a local Dockerfile whose RUN npm ci, npm install or npm prune commands make the same advisory lookup again. Several image layers can repeat the request, and a slow advisory service can hold up the image build.

Detection heuristic: Require both halves in one readable job. The host half is a direct npm ci that keeps audit on: its flags, step/job/workflow environment and every repository .npmrc from its effective working directory (defaults.run.working-directory included) up to the checkout root leave audit enabled, and it runs whenever the image build runs (no if:, or the build's own if:). The image half is a local Docker build whose selected stage, or a stage it builds from, runs npm ci, npm install or npm prune with audit still on after copying in that same host lockfile. Image audit settings are read as Docker applies them: ENV/ARG NPM_CONFIG_AUDIT, npm config set audit and an .npmrc copied into the image, in instruction order; a build-context .npmrc the Dockerfile never copies does not count. Heredoc bodies and quoted text are data, not commands. Expressions, cd/--prefix directory changes, remote contexts, unreadable files, unknown audit values, an unselected stage, a separate lockfile, and Docker commands that already disable audit stay quiet.

Fix recipe (safest first):

  1. Keep the host npm ci audit reporting unchanged so the job still reports advisories once.
  2. Add --no-audit only to each image-layer npm ci, npm install and npm prune that the finding names. Preserve lockfile resolution, lifecycle scripts, production pruning and every image input.
  3. Build the old and new image from the same lockfile, compare the application artifacts and installed production package versions/integrities, then run the image's existing smoke or syntax check.

Sizing: Runner-minute effect is a saving because the same image-build runner waits on fewer advisory requests. The static finding is unsized: it has neither measured Docker-layer duration nor the job's 30-day run count. Use matched before/after layer timings to size it; do not import another project's numbers as a forecast. Wall-clock also goes down only when these layers are on the job's gating path.

Public evidence:

Risk: LOW when the host audit remains mandatory. The change must not disable the last advisory report, alter dependency resolution or pruning, or skip the image's parity checks.

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