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.

referencespatternsopt113-oversized-test-fixture.md

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

OPT113 — A Test Fixture Is Much Larger Than Its Contract Needs

Anti-pattern: A test archives, compresses or hashes the linked Go test executable, or a binary it just built, when the contract under test only needs ordinary file bytes. The linked test binary can be many megabytes and grows further under instrumentation such as the race detector, so every repeated archive pays to move bytes the assertion does not distinguish.

Detection heuristic: In a Go _test.go file, find one function that opens or reads the linked test executable (os.Executable(), directly or through a helper that returns it) or the output of an explicit go build -o in that function, and passes those same bytes into a writer made by an archive, compression or hash constructor (or a direct digest call). A file that inspects format headers (debug/elf, debug/macho, debug/pe), verifies a signature, executes a binary, or asserts a file mode stays quiet: there the real binary is the contract. Reads of a different file beside the executable, and a small byte fixture going through the same archive path, also stay quiet. If the source cannot tie the executable bytes to the archive or hash, withhold the finding rather than guessing.

Fix recipe (safest first):

  1. State the contract the test exercises: ordinary bytes and their digest, archive layout, executable mode, platform metadata, or the built program's actual behavior.
  2. For byte, digest and layout checks, create one small shared fixture with deterministic bytes and pass it through every existing archive/compression assertion. Keep the modes, inventory entries, stale-hash rejection and extraction checks intact.
  3. Keep a real executable for cases that inspect executable metadata, execute the program, or validate a property that a byte fixture cannot represent.
  4. Compare the affected test lane before and after on the same commit, runner class and instrumentation mode; confirm the test and coverage inventory is unchanged.

Sizing: The static finding credits neither wall-clock nor runner-minutes. Runner-minute saving is unsized until run timings identify the affected test and its monthly execution count. As a public single-run observation, not a general estimate, openclaw/crabbox#2876 reported its package's race lane falling from 256.401 seconds to 61.720 seconds and the enclosing race job from 16m45s to 11m04s — a runner-time saving of 5m41s for that one observed run. The detector does not claim a merge-wait saving from source.

Risk: MEDIUM. Replacing a real artifact can weaken a test that checks permissions, architecture, signing, executable metadata or actual execution. Keep those cases on real artifacts and shrink only the fixtures whose contract is byte content, hashing or archive shape.

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