Commit Frequency

In one sentence

Commit frequency counts how often commits occur in a window; it describes activity cadence, not individual output quality.

Why it matters

Leaders sometimes chart commits per engineer. That chart is easy to game and easy to misread when agents generate many small commits.

How it works

• Choose a window and a ref (usually the default branch).
• Count commits, optionally grouping by author or day.
• Normalize for team size and working days if you compare teams.
• Interpret alongside change size, review lag, and outcome metrics—not alone.

Example

40 commits in a week from an agent loop fixing lint may look “productive” while delivering little accepted behavior change. Pair frequency with accepted-change and review evidence.