Measure change throughput

Situation: You want a point-in-time view of lead time for changes, merge frequency, contributor concentration, and whether the team is hitting a per-active-contributor benchmark — from local git only.

Run: change-throughput

Do not copy the skill procedure here. Confirm window, trunk branch, monorepo scope, and deploy trigger first (scope gate in the skill).

What a good outcome looks like

A single markdown report with:

Section	Content
At a glance	Window, branch, LTFC median/p75, DF (meaningful)/week, active count, benchmark %
Validation	Author≈committer dates; merge==deploy (or relabelled)
Contributors	Core / rotating / occasional; top-N concentration
Benchmark	Target vs actual for the window

Illustrative headline (Plumbing persona): 30d on main · LTFC median 4.2h · DF 6.1 meaningful/wk · 3 genuinely active · benchmark 87%.