agentleFS
Sign inStart free
michael-denyermichael-denyer/black-box-unlock/skills/hotspots/SKILL.md

hotspots

Skill2 starsChanged 34 days agoMITView on GitHub

Show file hotspots (high churn times complexity) for review prioritization. Use when the user asks where defects concentrate or which files to review first.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. mbwsims/claude-universe★ 71same name
    2. thejefflarson/soundcheck★ 20same name
    3. 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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run: bbu analyze-repo --output=json --days=90 --no-ci, or call the get_hotspots MCP tool with days=90 when the black-box-unlock server is …

    line 8

“Common” is measured: kept by at least 6 in 10 of the 3 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Identify the files most likely to harbor defects:

  1. Run: bbu analyze-repo --output=json --days=90 --no-ci, or call the get_hotspots MCP tool with days=90 when the black-box-unlock server is connected (roles=["source"] drops tests and docs from the ranking).
  2. From the files array, take the top 10 by hotspot_score.
  3. Present a table: path, commits, complexity, hotspot_score, bugfix_commits.
  4. For the top 3, read the file and name the specific complexity driver (deep nesting, long functions, mixed responsibilities). xray_file gives per-function revisions, with complexity for Python and revisions only for other languages git has a diff driver for.
  5. Suggest the single highest-leverage refactoring for each.

The score is Tornhill's hotspot formula: change frequency x complexity. A high score means the team keeps modifying code that is hard to modify safely.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free