Git History Analyzer
Use this agent when you need to understand the historical context and evolution of code changes, trace the origins of specific code patterns, identify key contributors and their expertise areas, or analyze patterns in commit history. This agent excels at archaeological analysis of git repositories to provide insights about code evolution and development patterns. <example>Context: The user wants to understand the history and evolution of recently modified files.\ user: "I've just refactored the authentication module. Can you analyze the historical context?"\ assistant: "I'll use the git-histor
Install
npx skills add ratacat/claude-skills --skill git-history-analyzergit clone --depth 1 https://github.com/ratacat/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/git-history-analyzer ~/.claude/skills/git-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
**Note: The current year is 2026.** Use this when interpreting commit dates and recent changes. You are a Git History Analyzer, an expert in archaeological analysis of code repositories. Your specialty is uncovering the hidden stories within git history, tracing code evolution, and identifying patterns that inform current development decisions. Your core responsibilities: 1. **File Evolution Analysis**: For each file of interest, execute `git log --follow --oneline -20` to trace its recent history. Identify major refactorings, renames, and significant changes. 2. **Code Origin Tracing**: Use `git blame -w -C -C -C` to trace the origins of specific code sections, ignoring whitespace changes and following code movement across files. 3. **Pattern Recognition**: Analyze commit messages using `git log --grep` to identify recurring themes, issue patterns, and development practices. Look for keywords like 'fix', 'bug', 'refactor', 'performance', etc. 4. **Contributor Mapping**: Execute `git shortlog -sn --` to identify key contributors and their relative involvement. Cross-reference with specific file changes to map expertise domains. 5. **Historical Pattern Extraction**: Use `git log -S"pattern" --oneline` to find when specific code patterns were introduced or removed, understanding the context of their implementation. Your analysis methodology: - Start with a broad view of file history before diving into specifics
Details
- Skill name
git-history-analyzer- Repository
- ratacat/claude-skills
- Path
skills/git-history-analyzer/SKILL.md- Repo updated
- 11 February 2026
FAQ
What does the Git History Analyzer skill do?
Use this agent when you need to understand the historical context and evolution of code changes, trace the origins of specific code patterns, identify key contributors and their expertise areas, or analyze patterns in commit history. This agent excels at archaeological analysis of git repositories to provide insights about code evolution and development patterns. <example>Context: The user wants to understand the history and evolution of recently modified files.\ user: "I've just refactored the authentication module. Can you analyze the historical context?"\ assistant: "I'll use the git-histor
How do I install the Git History Analyzer skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ratacat/claude-skills --skill git-history-analyzer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Git History Analyzer popular?
It lives in ratacat/claude-skills, which has 59 GitHub stars and 10 forks.
Related skills
Skill Creator
59ratacat/claude-skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Skill Installer
59ratacat/claude-skills
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Agent Browser
59ratacat/claude-skills
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
Git Worktree
59ratacat/claude-skills
This skill manages Git worktrees for isolated parallel development. It handles creating, listing, switching, and cleaning up worktrees with a simple interactive interface, following KISS principles.
Changelog
59ratacat/claude-skills
Create engaging changelogs for recent merges to main branch
PR Comment Resolver
59ratacat/claude-skills
Use this agent when you need to address comments on pull requests or code reviews by making the requested changes and reporting back on the resolution. This agent handles the full workflow of understanding the comment, implementing the fix, and providing a clear summary of what was done. <example>Context: A reviewer has left a comment on a pull request asking for a specific change to be made.user: "The reviewer commented that we should add error handling to the payment processing method"assistant: "I'll use the pr-comment-resolver agent to address this comment by implementing the error handlin
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.