Hotspot Analysis
Change frequency times complexity. Identifies places where the system is simultaneously difficult and frequently changed — more interesting than “files with the most lines.”
Hotspot analysis combines two signals: how complex a module is (cyclomatic complexity, nesting depth) and how often it changes (commit frequency). The intersection — a complex module that changes frequently — is where risk concentrates.
Sensor properties
| Property | Value |
|---|---|
| Oracle strength | Low — a hotspot is a risk indicator, not a bug |
| Independence | High — computed from git and metrics |
| Scope | Module-level |
| Feedback latency | Minutes |
| Actionability | Exploratory — shows the heat map |
| Type | Retrospective |
What it cannot detect
Hotspot analysis doesn’t tell you why a module changes frequently or whether it’s correct. It identifies where attention is needed, not what the attention should fix.