Dev loop audit

Measure where the development loop lost time last week, rank every problem by minutes lost, prove the top ones, and ask which fixes to build. Three areas, one ranking: CI (GitHub Actions), the gate (git hooks and the checks people run before a push), and agent time (what Claude Code spent waiting, retrying and checking its work on a simulator or in a browser). Agent time is often the biggest cost and the one nobody measures.

Talk to the person in short, plain sentences, with a recommendation. Every number comes from a script or a command; an estimate says "estimated". Read-only until the person picks fixes: the only files you write before that are the record and the trend row.

Scripts (Node 18+, no installs) are in ${CLAUDE_SKILL_DIR}/scripts/. Run them from the repo root. Put their output in a scratch folder ($OUT below), never in the repo.

1. Setup (first run only)

If the repo has no dev-loop-audit config (.dev-loop-audit/config.json, or ~/.claude/dev-loop-audit/<repo>/config.json), or $ARGUMENTS is setup, follow references/setup.md, then stop if the argument was setup.