hotspots
Skill0 starsChanged 15 days agoNo licenceView on GitHub
Find the code that costs the most to change and refactor it safely, behavior unchanged. Ranks source files from git history by churn, complexity, bug-fix commits and change coupling, shows the top hotspots and lets the user pick. Diagnoses each chosen file - long functions, mixed responsibilities, mixed abstraction levels, deep nesting, duplication, temporal coupling, hidden global state, unclear names, type switches that grow - with path and line evidence and history. Plans small behavior-preserving refactoring steps, has a skeptic challenge each, pins current behavior with characterization tests where coverage is missing, then applies the steps one at a time with tests after each, reverts any step that breaks something, keeps a ledger and measures before and after. Use when the user asks for hotspots, technical debt, the worst or riskiest code, what to refactor first, or a safe refactor of old code, or invokes /hotspots (options --scope, --since, --top, --report-only, --auto, --models). Commits nothing.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- michael-denyer/black-box-unlocktheir own version, first seen Oct 15, 2026
- thejefflarson/soundchecktheir own version, first seen Jul 31, 2026
- mbwsims/claude-universetheir own version, first seen Apr 14, 2026
- xltang/hotspotstheir own version, first seen Apr 9, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- mbwsims/claude-universe★ 71same name
- thejefflarson/soundcheck★ 20same name
- michael-denyer/black-box-unlock★ 2same name
- xltang/hotspots★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- conventionsSkill
- deep-reviewSkill
- dep-hygieneSkill
- deslopSkill
- error-pathsSkill
- guided-reviewSkill
- perf-passSkill
- pr-reviewSkill
- sdlc-fast-piSkill
- sdlc-fastSkill
- sdlc-loopSkill
- test-strengthSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. 0 are common, 12 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.