AI-assisted PRs counts pull requests with at least one commit that Leanmote tags as AI-authored, alongside the share of all PRs in the period that are AI-assisted. It's the simplest signal of how much AI-touched work flows through the team.
What it measures
For each PR in the period, Leanmote checks every commit in the PR. If at least one commit is AI-tagged, the PR is AI-assisted. The metric reports both the count and the share against total PRs.
How Leanmote tags an AI commit
A commit is tagged as AI-assisted when either of the following is true:
The commit's author had recorded AI activity (any event in the AI-tool fact data) on the same calendar day the commit was authored, AND the AI activity is associated with that author's identifier.
The commit message contains a
Co-authored-by:trailer matching a known AI identity (for example:github-copilot,copilot[bot],[email protected],claude,cursor-ai,cursor[bot],codeium,tabnine).
A PR is AI-assisted whenever any commit on the PR meets either condition.
Period scope
PRs are included in the period based on their creation date, not their merge date. A PR opened in the period but merged after still contributes; a PR opened earlier but merged in the period does not. The headline number you see (e.g., "AI-Assisted PRs 29.3% of all PRs") is the share among PRs created in the selected window.
How to interpret it
Rising count — adoption is growing. Compare to team size to see whether it's broadening or just deepening among existing users.
High share with AI Lead Time advantage — the team is getting measurable value from AI.
High share without measurable Lead Time advantage — adoption without impact. Investigate whether AI tools are being used effectively.
Sudden jumps — often caused by Co-authored-by trailers becoming enabled (or disabled) in your team's commit conventions, not actual usage shifts.
What to do about it
Pair this metric with AI Lead Time Comparison and AI Intensity for a complete adoption-and-impact picture.
Don't optimize for higher AI-assisted PR counts in isolation. The goal is delivery improvement, not AI usage.
Related metrics
AI-assisted Commits
AI Intensity
AI Lead Time Comparison
AI Return metrics overview