nw-hotspot

Featured

Git change frequency hotspot analysis — find the most-changed files in your codebase

AI & Automation 636 stars 68 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# NW-HOTSPOT: Code Crime Scene Hotspot Lens **Wave**: CROSS_WAVE **Execution**: Inline (no agent — Claude executes git commands directly) **Inspiration**: Adam Tornhill's "Your Code as a Crime Scene" ## Overview Analyze git change frequency to identify the most-changed files in a codebase. Pure git churn — no complexity metrics. Use as a **pre-filter** to scope analysis or a **post-filter** to prioritize existing findings. ## How It Works Run `git log --name-only` over the configured time period, count commits per file, rank by frequency. ## Modes ### 1. Analyze (default) Show the most-changed files in the repo. Output is inline only — no files persisted. ``` /nw-hotspot /nw-hotspot --top=20 /nw-hotspot --since=12m ``` **Steps:** 1. Run: `git log --since={since} --format=format: --name-only | sort | uniq -c | sort -rn` 2. Exclude deleted files (verify each file still exists with `test -f`) 3. For each file, get last changed date: `git log -1 --format="%ar" -- {file}` 4. Display ranked table (top N): ``` Rank │ Commits │ Last Changed │ File ──────┼─────────┼──────────────┼───────────────────────── 1 │ 87 │ 2 days ago │ src/services/payment.ts 2 │ 64 │ 1 week ago │ src/api/controllers/user.ts 3 │ 51 │ 3 days ago │ src/models/order.ts ``` 5. Show summary: total files changed in period, time period, top N shown **Defaults:** `--top`: 15, `--since`: 6 months ### 2. Rank (post-filter) Overlay churn data on an existing analysis report...

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

Code & Development Listed

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".

0 Updated 3 days ago
vivekbhange-hub
AI & Automation Listed

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".

0 Updated 3 days ago
vivekbhange-hub
AI & Automation Listed

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.

2 Updated 1 months ago
risadams