nw-hotspot
Git change frequency hotspot analysis — find the most-changed files in your codebase
Install / Use
npx skills add nWave-ai/nWave --skill nw-hotspotInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of nw-hotspot
nw-hotspot scores 84/100 on our quality scale, 2973rd of 4,702 Development & Engineering skills we index.
Its SKILL.md is 4.6 KB long, well organised into 21 sections with 9 code examples: a solid amount of guidance for an agent.
It has 617 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so nw-hotspot is actively maintained.
- Our last check on 2026-11-06 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-09. Automated pattern scan on 2026-10-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
nw-hotspot compared with similar skills
All 4 of these similar skills score higher than nw-hotspot; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| nw-hotspot (this skill)by nWave-ai | 84 | 617 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
Frequently asked questions
- How do I install nw-hotspot?
- Run
npx skills add nWave-ai/nWave --skill nw-hotspot. The install tabs above show the steps for each supported agent. - Which AI agents does nw-hotspot work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is nw-hotspot safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is nw-hotspot still maintained?
- The repository was last updated about 2 months ago, so nw-hotspot is actively maintained.
Skill content
View source on GitHubname: nw-hotspot description: "Git change frequency hotspot analysis — find the most-changed files in your codebase" user-invocable: true argument-hint: '[--top=N] [--since=6m] [--json] [--rank report.md] [--detail file]'
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:
- Run:
git log --since={since} --format=format: --name-only | sort | uniq -c | sort -rn - Exclude deleted files (verify each file still exists with
test -f) - For each file, get last changed date:
git log -1 --format="%ar" -- {file} - 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
- 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 to prioritize findings.
/nw-hotspot --rank code-smell-detector-report.md
Steps:
- Run the same git churn analysis
- Read the specified report file
- Extract file paths mentioned in the report
- Annotate each file with its commit count
- Re-sort findings by churn (highest first). Findings without extractable file paths go at the bottom.
- Show noise reduction: "X of Y findings are in low-churn files (< 20 commits)"
3. Detail (deep-dive)
Deep-dive into a single file's change history.
/nw-hotspot --detail src/services/payment.ts
Steps:
- Monthly commit breakdown over the period
- Top contributors to the file
- Co-change coupling: top 5 files that frequently change alongside this one
- Last 10 commit messages for context
4. JSON export (pre-filter composition)
/nw-hotspot --top=10 --json
Output: [{"path": "src/services/payment.ts", "commits": 87, "last_changed": "2 days ago"}, ...]
Parameters
| Flag | Default | Description |
|------|---------|-------------|
| --top | 15 | Number of files to show |
| --since | 6m | Time period (e.g., 3m, 12m, 2024-01-01) |
| --json | false | Output as JSON array |
| --rank | - | Path to existing report to re-rank by churn |
| --detail | - | Path to single file for deep-dive |
Edge Cases
- No commits in period: Display "No commits found since {date}" rather than an empty table
- File renames: Counted as separate files (no
--follow; keeps it simple and fast) - Empty repo / not a git repo: Display error and exit
Usage from Other Skills
Pre-filter (scope downstream analysis)
Run /nw-hotspot --top=10 --json first, then pass the file list to:
- code-smell-detector: "Analyze only these files: {hotspot list}"
- cognitive-load-analyzer: "Focus analysis on these files: {hotspot list}"
- refactoring-expert: "Prioritize recommendations for these files"
Post-filter (rank existing findings)
Run /nw-hotspot --rank {report.md} after any analysis to prioritize by churn.
In nWave workflows
- Before
/nw-refactor— identify which files to refactor first - Before
/nw-review— focus review effort on high-churn areas - Before
/nw-root-why— check if the problematic area is a known hotspot
Next Wave
Usage Context: Inline utility, composable with any analysis skill Handoff To: Invoking context (no sequential handoff)
Examples
Example 1: Quick scan of a legacy codebase
/nw-hotspot
Example 2: Scope a code smell analysis to hotspots
/nw-hotspot --top=10 --json
Example 3: Prioritize an existing refactoring report
/nw-hotspot --rank code-refactoring-report.md
Example 4: Investigate a specific troubled file
/nw-hotspot --detail src/services/payment.ts
Expected Outputs
No persistent files. Output is displayed inline. JSON mode outputs a JSON array for composition with other tools.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
