hotmess
Skill32 starsChanged 4 months agoNo licenceView on GitHub
Find and explain churn hotspots and unstable code clusters in a git repo. Goes beyond a flat "most-edited files" list — auto-detects clusters by directory, by filename stem (foo.go + foo_test.go), and by co-change (files that change together) — then classifies each cluster (unstable / under-development / buggy / tightly-coupled / spec-shifting) and explains *why* it's a problem. Trigger whenever the user asks about churn, hotspots, unstable code, files that change a lot, refactoring candidates, technical debt hotspots, "what's a mess", "/hotmess", or any combination of folder + time window where they want insight rather than just numbers. Auto-detects code files when no extension is given.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/api-dog-food.mdCursor rule
- .cursor/rules/cloc.mdCursor rule
- .cursor/rules/continue-loop.mdCursor rule
- .cursor/rules/dotnet-strict.mdCursor rule
- .cursor/rules/hotmess.mdCursor rule
- .cursor/rules/palette.mdCursor rule
- .cursor/rules/pre-pr.mdCursor rule
- .cursor/rules/profile.mdCursor rule
- .cursor/rules/quickdup.mdCursor rule
- .cursor/rules/roslynator.mdCursor rule
- .cursor/rules/systematic-debug.mdCursor rule
- .cursor/rules/testrunner.mdCursor rule
- .cursor/rules/uxly.mdCursor rule
- api-dog-foodSkill
- clocSkill
- continue-loopSkill
- dotnet-strictSkill
- paletteSkill
- pre-prSkill
- profileSkill
- quickdupSkill
- roslynatorSkill
- systematic-debugSkill
- testrunnerSkill
- uxlySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
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 an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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.