nw-hotspot
FeaturedGit change frequency hotspot analysis — find the most-changed files in your codebase
Install
Quality Score: 95/100
Skill Content
Details
- Author
- nWave-ai
- Repository
- nWave-ai/nWave
- Created
- 9 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
gitfx-hotspots
Ranks the files in a git repository that are both changed often and expensive to change (churn times size and nesting), shows commits, lines, authors and fix share for each, explains why each one is a hotspot and says where refactoring or tests would pay off most. Reads git history only and never loads it into the conversation. Use when the user says "where is this codebase fragile", "find the hotspots", "which files change the most", "what should we refactor first", "where do bugs cluster", or "which files need tests".
rescue-hotspots
Finds where the risk in a legacy codebase concentrates by crossing git history with code complexity: files that change often and are hard to read, pairs of files that always change together, and busy files only one person has touched. Runs a bundled script over git log and writes rescue/hotspots.md with a ranked table and a short reading of what it means. Use when the user says "where is the risky code", "find the hotspots", "what should we refactor first", "which files break the most", "show me code churn", "what changes together", or "who knows this code".
codebase-churn
Analyze a git repository's history and produce an SVG treemap of file churn — area = lines changed, color = commit frequency. Use when user wants to find unstable areas of a codebase, predict bug-prone files, see "where do we change the most", spot refactor candidates, or invokes /codebase-churn.