ci-speeduplisted

# ci-speedup — CI Optimization Audit for GitHub Actions Audits a repository's GitHub Actions workflows against a 73-pattern catalog — 67 **hygiene/data-driven** patterns plus 6 **structural / critical-path** patterns routed from the measured long pole — and produces a **root-cause-analysis** report with measured impact on two axes — developer wall-clock wait and runner-minutes (cloud bill). The report opens with a **Long poles** section — the checks that gate the merge (how often each is the pole across sampled PRs, and a per-step breakdown showing the root-cause step) — then a **Findings** section: each detected inefficiency, ranked by measured impact, presented as a root-cause observation with its evidence. **ci-speedup does NOT prescribe the fix.** Detection + run-history measurement are accurate; *fixes* are where a generic tool goes wrong (no file intent, real logs, or load-bearing context). So **every finding ships a ready-to-paste agent prompt** handing the pattern + measured cost to the user's coding agent, which investigates the real runs/logs/intent and reasons out the safe remedy — measured diagnosis from the tool, fix from an agent that sees the code. ## The report — a wall-clock critical path The report **is** the measured wall-clock critical path: each merge-gating long pole drilled from the gate down to its root cause, headlined by the single biggest measured win (developer wait removed from the critical path). **Pre-start wall-clock wait (queue time, OPT43