Commit counts measure habits, not work
Some developers commit every ten minutes, others once a day. Counting commits rewards the habit, not the work. Lines changed are no better: a generated lockfile or a reformat can add thousands of lines without any thought behind them.
Commit effort replaces the count with a reading. Each commit is summarized in one or two lines and scored from 1 to 10 for the work it represents: a typo is a 1, a configuration change a 2 or 3, a new endpoint with tests a 7, a feature touching several layers an 8 or 9. A 10 is exceptional.
Effort is the sum
A person’s effort over a period is the sum of their scores. Three label fixes rated 1 make 3 points; one feature rated 9 makes 9. The ranking on the dashboard and in reports follows the work, not the number of commits. Generated files, vendored dependencies and pure reformatting are recognised and score low whatever their size.
How the score is produced
When a commit lands on a tracked branch, its diff is loaded in memory, read by Squadlog’s own model, summarized and scored. The diff is then discarded; only the line and the score are kept. The same model and the same scale apply to every repository, so scores are comparable across a team.
What the score is not
It is not a rating of a developer. It describes a commit. It is shown next to the commit, averaged per person for context, and summed for the ranking, but there is no threshold on people, no alert based on a low score and no automated decision of any kind.