From sourceatlas
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sourceatlas:history-analyzerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Trigger this skill when the user:
Trigger this skill when the user:
/sourceatlas:history for the entire repo, or /sourceatlas:history <path> for specific directory/sourceatlas:history . 6 for last 6 months/sourceatlas:history/sourceatlas:history src//sourceatlas:history . 6 (last 6 months)npx claudepluginhub lis186/sourceatlas --plugin sourceatlasAnalyzes repository git history, code coupling, bus factor, bugspots, ownership, entry points, and repo health signals on demand.
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.
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.