Stats
Actions
Tags
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/composto:composto-trendsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze codebase health over time using git history. Zero LLM tokens — all analysis is local.
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 fragilenpx claudepluginhub mertcanaltin/composto --plugin compostoAnalyzes git history to detect churn hotspots and unstable code clusters, classifying them by cause (unstable, buggy, tightly-coupled, etc.) with explanations. Used when asked about hotspots, technical debt, or "what's a mess" in a repo.
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.
Analyzes git history to identify code hotspots, bug magnets, bus factor, team momentum, and recent changes. Use when onboarding to unfamiliar codebases or assessing project health.