History Analyzer
Analyze git history for hotspots, coupling, and knowledge distribution. Use when user asks "who knows this code", "what files change most", "hotspots", "bus factor", "knowledge silos", or needs to understand code evolution.
Install
/plugin marketplace add lis186/SourceAtlasThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lis186/SourceAtlas --skill history-analyzergit clone --depth 1 https://github.com/lis186/SourceAtlas.git /tmp/SourceAtlas
mkdir -p ~/.claude/skills
cp -r /tmp/SourceAtlas/plugin/skills/history-analyzer ~/.claude/skills/history-analyzerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# History Analyzer ## When to Use Trigger this skill when the user: - Wants to find code hotspots (frequently changed files) - Needs to identify who knows specific code areas - Asks about bus factor or knowledge distribution - Wants to find hidden coupling between files - Asks "who should I ask about X" ## Instructions 1. Run `/sourceatlas:history` for the entire repo, or `/sourceatlas:history <path>` for specific directory 2. Optionally specify time range: `/sourceatlas:history . 6` for last 6 months 3. Returns hotspots, coupling analysis, and contributor distribution ## Command Formats - Full repo: `/sourceatlas:history` - Specific directory: `/sourceatlas:history src/` - With time range: `/sourceatlas:history . 6` (last 6 months) ## What User Gets - Hotspots: Files with most changes (complexity indicators) - Temporal Coupling: Files that always change together (hidden dependencies) - Recent Contributors: Who knows what areas - Bus Factor Risk: Single-contributor files - Priority actions for refactoring ## Example Triggers - "What are the hotspots in this codebase?" - "Who knows the payment module best?" - "What files always change together?" - "Is there any bus factor risk?" - "Show me knowledge distribution"
Details
- Skill name
history-analyzer- Repository
- lis186/SourceAtlas
- Path
plugin/skills/history-analyzer/SKILL.md- License
- MIT
- Repo updated
- 22 October 2026
FAQ
What does the History Analyzer skill do?
Analyze git history for hotspots, coupling, and knowledge distribution. Use when user asks "who knows this code", "what files change most", "hotspots", "bus factor", "knowledge silos", or needs to understand code evolution.
How do I install the History Analyzer skill?
Claude Code plugin: /plugin marketplace add lis186/SourceAtlas. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is History Analyzer popular?
It lives in lis186/SourceAtlas, which has 49 GitHub stars and 4 forks.
Related skills
Code Flow Tracer
49lis186/SourceAtlas
Trace code execution paths and data flow. Use when user asks "how does X work", "what happens when X", "trace the flow of X", "where does data come from", or needs to understand feature implementation.
Codebase Overview
49lis186/SourceAtlas
Quickly understand a new codebase's architecture, tech stack, and patterns. Use when user asks "what is this project", "project overview", "how is this codebase structured", "what tech stack", or when onboarding to a new codebase.
Dependency Analyzer
49lis186/SourceAtlas
Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.
Impact
49lis186/SourceAtlas
Analyze the impact scope of code changes using static dependency analysis
Deps
49lis186/SourceAtlas
Analyze dependency usage for library/framework/SDK upgrades
Impact Analyzer
49lis186/SourceAtlas
Analyze what code will be affected by changes. Use when user asks "what will break if I change X", "impact of changing X", "dependencies of X", "is it safe to modify X", or before making significant code changes.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.