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.
When & Why to Use This Skill
The History Analyzer is a specialized Claude skill designed for deep Git repository forensics and codebase health assessment. It empowers developers and engineering managers to visualize code evolution by identifying high-churn 'hotspots,' uncovering hidden file dependencies through temporal coupling, and mapping knowledge distribution across the team. By providing data-driven insights into the 'bus factor' and contributor expertise, it helps teams mitigate technical debt, streamline onboarding, and make informed refactoring decisions.
Use Cases
- Technical Debt Prioritization: Identify 'hotspots'—files with high change frequency and complexity—to determine where refactoring will have the highest impact.
- Knowledge Distribution & Onboarding: Map which contributors are most active in specific modules to find the right subject matter experts for code reviews or architectural questions.
- Risk Mitigation: Detect 'bus factor' risks by identifying critical components maintained by a single person, enabling proactive knowledge sharing.
- Dependency Analysis: Discover 'temporal coupling' where files consistently change together, revealing hidden architectural dependencies that aren't obvious from the code alone.
- Legacy Code Exploration: Understand the evolution of a codebase over specific timeframes to grasp how and why certain modules have changed.
| name | history-analyzer |
|---|---|
| description | 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. |
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
- Run
/sourceatlas:historyfor the entire repo, or/sourceatlas:history <path>for specific directory - Optionally specify time range:
/sourceatlas:history . 6for last 6 months - 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"