churn_vs_complexity

https://github.com/beatmadsen/churn_vs_complexity

Correlates file churn (how often files change) with complexity scores to identify refactoring hotspots. Supports Ruby, JavaScript/TypeScript, Java, Python, and Go. Modes include hotspots ranking, triage assessment, CI quality gate, diff comparison, focus sessions, and timetravel history. Inspired by Michael Feathers' article "Getting Empirical about Refactoring".