From composto
Analyzes git history to detect codebase hotspots (frequent changes/bug fixes), decay signals (accelerating churn), and inconsistencies (multiple authors/patterns). Use before refactoring or investigating recurring bugs.
npx claudepluginhub mertcanaltin/composto --plugin compostoThis skill uses the workspace's default tool permissions.
Analyze codebase health over time using git history. Zero LLM tokens — all analysis is local.
Analyzes git history to find code hotspots, temporal coupling between files, contributor knowledge distribution, and bus factor risks. Useful for queries on code ownership, frequent changes, or evolution.
Identifies and explains churn hotspots and unstable code clusters in git repos. Groups by directory, filename stems (e.g. foo.go + foo_test.go), and co-changes; classifies as unstable, buggy, tightly-coupled, etc.
Identifies riskiest codebase files using git churn analysis, complexity metrics, coupling, and lenskit risk scores for technical debt hotspots.
Share bugs, ideas, or general feedback.
Analyze codebase health over time using git history. Zero LLM tokens — all analysis is local.
npx composto trends .
Files that change too often with too many bug fixes:
src/auth/session.ts — 12 changes, 67% fixes, 3 authors
This means: this file is a problem area. It keeps breaking and different people keep patching it differently.
Areas where churn is accelerating — more changes happening in recent time than before:
src/auth/session.ts — churn is declining
"Declining" means the health is declining (churn is increasing).
Files where many different authors have made changes, potentially with different patterns:
src/auth/session.ts — 3 different patterns
If a file shows up as a hotspot:
composto-ir <file> L1 to see its Health-Aware IR with annotations[HOT:12/30 FIX:67%] so any LLM working on it knows it's fragile