Git History Analyzer

DocumentationIntermediate

Analyzes commit history, branch patterns, and file change frequency to visualize project hotspots, contributor patterns, and technical debt locations.

Trigger/history

FrequencyMonthly

Engineering manager? Run /history to identify team code contribution patterns and hotspots

Developer joining a legacy project? Most frequently changed files = refactoring priorities

GitHistoryAnalyticsTechnical Debt

How It Works

Run /history -> collect commit logs

↓

Phase 1: 3 analyses in parallel

hotspot-find

Detect change hotspots

contrib-map

Analyze contributor patterns

churn-calc

Calculate code churn rate

↓

Synthesize insights

↓

✓ Hotspot map + contribution stats + technical debt locations

Skill Code

# Git Historian Skill
## Trigger: /history [time range]

When invoked:

1. Collect git data:
 - `git log --stat` for change frequency
 - `git shortlog -sn` for contributor stats
 - `git log --diff-filter=M` for modification patterns

2. Analyze patterns:
 - Files changed most often (hotspots)
 - Code churn (added then quickly deleted)
 - Coupling (files that always change together)
 - Contributor distribution per directory

3. Output format:
---
## 📜 Git History Analysis

### Change Hotspots (most modified files)
| File | Changes | Last Modified | Risk |
|------|---------|--------------|------|
| [file] | [N times] | [date] | 🔴 |

### Code Churn (high add/delete ratio)
| File | Added | Deleted | Churn Rate |
|------|-------|---------|-----------|

### Coupled Files (always change together)
- [file A] ↔ [file B] (X% co-change rate)

### Contributor Map
| Directory | Primary | Reviewers |
|-----------|---------|-----------|

### Insights
- [hotspot that needs refactoring]
- [area with single point of failure]
---

Copy and paste into your CLAUDE.md to start using immediately.

How Git History Analyzer Works

Git Historian analyzes your repository's commit history to extract patterns — most changed files, contribution frequency, technical debt hotspots, and development velocity — presenting insights in a structured report.

When to Use Git History Analyzer

Valuable during sprint retrospectives or when onboarding to a new codebase — it reveals which areas of the code change most frequently (potential refactoring targets) and how the project has evolved over time.

Key Strengths

Identifies technical debt hotspots from change frequency
Visualizes contribution patterns across team members
Reveals development velocity trends over time
Helps prioritize refactoring with data-driven insights

Same Category

Documentation View All

API Design Assistant

Designs RESTful APIs and auto-generates docs and type definitions.

Auto Doc Generator

Analyzes code and auto-generates API docs and usage guides.

README Generator

Analyzes your project and auto-generates a polished README.md.

Popular in Other Categories

Session Summary

WorkflowAutomatically summarizes changes and next steps at the end of a work session.

Smart Commit

CodingAnalyzes changes and auto-generates meaningful commit messages.

CLAUDE.md Builder

ProductivityAnalyzes your project and auto-generates an optimized CLAUDE.md.