19
High-Churn Files (50+)
1,546
TODO/FIXME Comments
45
any Types (Non-Generated)
80
console.log Statements
Most Changed Files (All Time)
High-Churn Files by Category
Top 20 High-Churn Files
| File Path | Changes | Category | Risk |
|---|
Code Quality Debt Indicators
How This Data Was Gathered
This analysis identifies files with concentrated maintenance burden using git history analysis.
Data Sources
- File change counts:
git log --all --pretty=format: --name-only | sort | uniq -c | sort -rn - High-churn threshold: Files with 50+ recorded changes
- TODO/FIXME:
grep -r "TODO\|FIXME" src --include="*.tsx" | wc -l= 1,546 - any types (non-generated):
grep -r ": any" src --include="*.tsx" --exclude-dir=generated | wc -l= 45 - console.log:
grep -r "console.log" src --include="*.tsx" | wc -l= 80
What This Means
- High-churn files: Frequently modified files may indicate poor abstraction, unclear requirements, or bug-prone code
- TODO/FIXME: Accumulated notes that may represent forgotten tasks or known issues
- any types: With only 45 instances in non-generated code, type safety is excellent
- console.log: Debug statements that should be removed before production
Recommendations
- Prioritize refactoring App.tsx (272 changes) by extracting routing and provider setup
- Review generated API files - high change counts are expected for generated code
- Consider splitting large screen files (InventoryBody, CatalogScreen) into smaller components
- Audit TODO/FIXME comments to close, convert to tickets, or remove outdated ones
Data collected: January 05, 2026