SkillAgentSearch skills...

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-hotspot

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Supported Platforms

Claude Code

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.

Substance
26/30
Structure
20/20
Description
12/15
Adoption
12/20
Freshness
15/15

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 found

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.

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.

SkillScoreStarsUpdatedFormat
nw-hotspot (this skill)by nWave-ai846172mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
Agent-Reachby Panniantong100112.7k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.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.

name: 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:

  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
  1. 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:

  1. Run the same git churn analysis
  2. Read the specified report file
  3. Extract file paths mentioned in the report
  4. Annotate each file with its commit count
  5. Re-sort findings by churn (highest first). Findings without extractable file paths go at the bottom.
  6. 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:

  1. Monthly commit breakdown over the period
  2. Top contributors to the file
  3. Co-change coupling: top 5 files that frequently change alongside this one
  4. 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

View on GitHub
GitHub Stars617
CategoryDevelopment
Updated2mo ago
Forks63

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions