Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-hotspot
Git change frequency hotspot analysis — find the most-changed files in your codebase
Passed 11 of 18 test cases with the skill, and 4 of 18 without it.
and 7 more in the full report
9 fixed5 passed either way9 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
When specifying a 12-month analysis window for git churn, which command line flag and argument value should be provided?
| Checked | Without skill | With skill |
|---|---|---|
| Uses --since=12m to set a 12-month analysis window. | Missed | Passed |
The instructions your model reads when the skill loads.
Wave: CROSS_WAVE Execution: Inline (no agent — Claude executes git commands directly) Inspiration: Adam Tornhill's "Your Code as a Crime Scene"
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.
Run git log --name-only over the configured time period, count commits per file, rank by frequency.
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:
git log --since={since} --format=format: --name-only | sort | uniq -c | sort -rntest -f)git log -1 --format="%ar" -- {file} 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
test cases passed, vs 4 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.