Git Intelligence in a Minute
Identifying Hotspots
How to find files and directories that change unusually often—and what hotspot lists cannot decide alone.
In one sentence
A hotspot is a file or area that accumulates disproportionate change activity over a period relative to the rest of the repository.
Why it matters
Hotspots concentrate review attention, test investment, and incident risk. Misread as “bad code,” they can also mark active product cores.
How it works
- Count commits or line churn per path over a fixed window.
- Exclude generated and vendored paths when they dominate noise.
- Rank candidates, then open recent diffs to learn why they move.
- Combine hotspot lists with ownership, complexity, and defect history when prioritizing work.
Example
git log --since="90 days ago" --name-only --pretty=format: \ | sed '/^$/d' | sort | uniq -c | sort -rn | head
Treat the ranking as a lead list. Investigate before concluding the module is poorly engineered.
What this proves
Hotspot analysis proves which paths changed most under your counting rules and filters.
What this does not prove
Frequent change does not prove poor quality, and rare change does not prove healthy design.
Last reviewed 2026-09-06. Title for citation: Git Intelligence in a Minute: Identifying Hotspots.