nw-hotspot

You identify the most-changed files by analyzing git commit history to calculate code churn and surface hotspots. This highlights high-churn areas to help prioritize code reviews and refactoring efforts.

Git churn analysis calculates how frequently files are modified by examining commit history. It helps code review by pinpointing unstable hotspots where defects are likely to cluster, focusing attention on high-risk areas.

Yes, you can analyze git hotspots in large repositories. The calculation applies git log-based churn analysis across small to large codebases, excluding deleted files to accurately rank current hotspots.

Use code churn metrics to pre-filter downstream analysis by scoping your review to only the top-churn files. You can also post-filter existing findings to reorder and prioritize results based on file modification frequency.

Yes, the git hotspot analysis supports JSON export alongside Analyze, Rank, and Detail modes. This allows you to integrate churn metrics directly into inline automated workflows.

Deleted files are excluded when calculating file churn from git history. This ensures the analysis only ranks and surfaces hotspots for files that currently exist in the codebase.