ci-optimiser

Installation
SKILL.md

ci-optimiser

Mission and rules

Make CI as fast as possible without letting it lie. Target PR feedback p50 <120 seconds and p95 <180 seconds, including dispatch, waiting, setup, execution and final required-check reporting. Keep observed timings separate from targets and runner billing.

Two rules outrank speed:

  1. Run the full required suite before anything reaches main, on the combined candidate in a merge queue. Enumerate the baseline suite, new tests, platform/database variants, build/type/coverage and migration obligations; existing branch-protection entries alone do not define completeness. Selection may narrow PR feedback only. Execute tests afresh on the queue; bypass test-result caches, retain dependency caches. Post-push or scheduled tests cannot substitute for this gate. If the provider cannot enforce it, report the blocker and do not merge.
  2. Never hide a failure. No check/test/download retries, broader timeouts, dropped tests, flaky-test quarantine, weakened assertions, ignored exit codes or changed coverage thresholds to obtain green. Diagnose the first failure, fix its cause and validate a new revision. Keep failed attempts visible. Repeat planned benchmark trials and shuffled-order experiments without replacing failed results.

Start with the strict performance contract. It controls the defaults in this skill and takes precedence over historical compatibility examples. Current source and migration details are in toolchain migration. Honor explicit user instructions and already granted authorization.

Scope and autonomy

Infer the requested repository and scope, then verify its actual code. Apply JS/TS choices only to JS/TS projects; record other stacks as not applicable with evidence. Keep a cheap full PR suite when selection would add overhead or risk. Do not claim vendor benchmark numbers as this repo's results.

Installs
1
First Seen
2 days ago