AI-assisted Commits counts commits made on a day when the author had recorded AI tool activity. It's a finer-grained version of AI-assisted PRs that captures the actual code-authoring touch points.
What it measures
The number of commits in the period where the commit author had at least one AI-tool event on the same calendar day.
How Leanmote calculates it
ai_assisted_commits = count(commits c in period where ai_active(c.author, c.committed_at))
ai_active(user, date)matches the same logic as AI-assisted PRs: at least one AI-tool event for the user on that date.Bot, revert, and merge commits are excluded.
Squash-merged commits count once at the squash level, not for the underlying commits.
How to interpret it
Compare to the total commit count. AI-assisted Commits / Total Commits gives a daily commit-share that's often more responsive than the PR-level metric.
High commit share with low PR share — AI is touching many small commits but not always making it into merged PRs.
Low commit share with high PR share — AI tools are used to start work, but most commits in the PR were non-AI iterations.
What to do about it
Use this as a sanity check on AI-assisted PRs — they should generally trend together.
If commit-level AI usage is high but PR-level adoption is low, investigate whether AI work is hitting friction in review.
Related metrics
AI-assisted PRs
AI Lines of Code
AI Intensity