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.

49 stars 4 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lis186/SourceAtlas

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lis186/SourceAtlas --skill history-analyzer
Manual install
git 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-analyzer

Personal 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"
Read the full skill on GitHub

Details

Skill name
history-analyzer
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

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.