ci-audit

1# /ci-audit — Find and fix wasted GitHub Actions time
2 
3Measure first, then fix the few things that matter. In real audits the biggest win was rarely a slow test suite. It was a scheduled pipeline that had failed every day for months, a 30-second hourly cron billed as 730 minutes a month, or an SDK silently retrying a dead request three times.
4 
5A stdlib script, `scripts/ci_audit.py` in this skill's folder, does the measuring. You read its output, decide what's worth fixing, and ship it.
6 
7```bash
8python3 <skill-dir>/scripts/ci_audit.py inventory <owner>              # which repos run Actions, private vs public
9python3 <skill-dir>/scripts/ci_audit.py month <owner/repo>             # billable minutes by workflow, 30 days
10python3 <skill-dir>/scripts/ci_audit.py jobs <owner/repo> --runs 150   # queue / setup / run per job
11python3 <skill-dir>/scripts/ci_audit.py steps <owner/repo> <run-id>    # per-step seconds for one run
12python3 <skill-dir>/scripts/ci_audit.py schedules <owner/repo>         # every cron as runs per month
13```
14 
15It needs the GitHub CLI (`gh`) logged in. `month` and `jobs` make one API call per run, so a busy repo takes a minute or two. Run them in the background.
16 
17## Step 0 — Scope and rules
18 
19Before measuring, settle with the user:
20 
21- **Which owners and repos.** One repo, or everything pushed to in the last 60 days.
22- **Off-limits repos.** Someone else (a teammate, another agent) is mid-feature there. Those get an issue with numbers, never a pushed branch.
23…