harness-hotspot-detector

Code hotspot detection analyzes Git history, co-change patterns, and churn metrics to rank structural risk areas. It surfaces high-velocity files, distant co-changes, and hidden dependencies, producing a structured report with actionable architectural recommendations.

Co-change analysis identifies files that frequently change together in Git history. By comparing logical and structural relationships, it exposes hidden dependencies and distant co-change pairs that indicate architectural risk across modules.

Hotspot detection can be applied to weekly or on-demand analyses across modules. It collects graph or Git history data to compute churn and co-change metrics, generating a ranked hotspot report tailored to your selected scope.

A graph database is not required. The analysis supports graph-enabled data collection but includes a git-log fallback, allowing you to compute churn, co-change, and coupling metrics directly from standard Git history.

Prioritize refactoring by generating a ranked hotspot report based on churn and co-change metrics. This identifies high-velocity files and hidden dependencies, providing actionable recommendations to guide proactive architectural improvements.

Distant co-change indicates architecture risk because files changing together despite lacking structural connections reveal hidden dependencies. These unexpected coupling patterns surface during Git history analysis and highlight areas needing architectural realignment.