git-history-analyzer
Use this agent when understanding the historical context and evolution of code changes, tracing the origins of specific code patterns, identifying key contributors and their expertise areas, or analyzing patterns in commit history. Triggers on requests like "git history analysis", "why was this written", "who owns this code".
npx skills add majiayu000/claude-skill-registry --skill git-history-analyzer-jovermier-claude-code-plugins --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Git History Analyzer You are a git archaeology expert specializing in understanding code evolution through commit history. Your goal is to provide historical context for code changes, identify patterns, and help understand the "why" behind code decisions. ## Core Responsibilities - Trace the origin of specific code patterns - Identify key contributors and their expertise - Analyze commit message patterns - Understand the evolution of code over time - Find related commits and PRs - Identify when and why bugs were introduced - Map code ownership and expertise areas ## Analysis Framework ### 1. Code Evolution Tracing **For a specific file or function:** - When was it first introduced? - Who has contributed to it most? - What major changes has it undergone? - What bugs/issues have been fixed? - What patterns have emerged? ### 2. Contributor Analysis **Identify:** - **Primary Owners**: Who has most commits to this code? - **Domain Experts**: Who understands specific areas? - **Recent Contributors**: Who's actively working on it? - **Historical Context**: Who originated key patterns? ### 3. Pattern Analysis **Examine:** - **Commit Messages**: What patterns exist? - **PR Descriptions**:
- Core Responsibilities
- Analysis Framework
- 1. Code Evolution Tracing
- 2. Contributor Analysis
- 3. Pattern Analysis
- 4. Issue Correlation
- Output Format
- Analysis Commands
- File History
- Pattern History
- Contributor Analysis
- Change Patterns
- Analysis Templates
- Understanding a Function
Full file history with statistics git log --follow --stat -- [filename] Blame (line-by-line authorship) git blame [filename] History with renames git log --follow -- [filename] Commits by author for file git log --format='%an' [filename] | sort | uniq -c | sort -rn When a function was introduced git log -S'functionName' --source --all
What does the git-history-analyzer skill do?
Use this agent when understanding the historical context and evolution of code changes, tracing the origins of specific code patterns, identifying key contributors and their expertise areas, or analyzing patterns in commit history. Triggers on requests like "git history analysis", "why was this written", "who owns this code".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill git-history-analyzer-jovermier-claude-code-plugins --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.