Git History Explorer — Research agent for Claude Code
MUST USE when searching git history to understand code evolution, find feature introductions, trace bug origins, or discover implementation patterns.
How to install Git History Explorer
Installs to ~/.claude/agents/wyattjoh-skills-git-history-explorer.md
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/wyattjoh/skills/HEAD/agents/git-history-explorer.md -o ~/.claude/agents/wyattjoh-skills-git-history-explorer.md Restart Claude Code, or start a new session, for it to be picked up.
What Git History Explorer does
name: git-history-explorer description: "MUST USE when searching git history to understand code evolution, find feature introductions, trace bug origins, or discover implementation patterns. Use PROACTIVELY for git log analysis, commit searches, blame investigations, and code archaeology." tools: "Bash, Grep, Glob, Read" permissionMode: plan
You investigate git history to explain how and why code reached its current state: when a feature or bug was introduced, which commits are related,
Alternatives in Research
- Scout — You are a specialized internal research agent 3.6k ★
- Context Explorer — Iteratively explore an unfamiliar codebase using semantic search 3.1k ★
- Deep Research Patcher — Applies critic findings to a nav-deep-research draft as surgical Edit hunks and records a patch log 232 ★
Full documentation available on GitHub
View Source RepositoryRelated Agents
House Git
Git analysis specialist. Use proactively for reviewing diffs (100+ lines), commit history analysis, branch com
GitOps
Git operations specialist. MUST BE USED for branch management, conflict resolution, git history analysis, work
Researcher Sonnet
Default research tier. Standard codebase investigation — how a feature is wired, what a change would touch, wh
Code Historian
Code evolution and history analysis expert that tracks how code has changed over time, who changed it, and pat
Planner Researcher
Use this agent when you need to research, plan, and architect technical solutions. This includes: searching fo
Doc Drift Auditor
Verify documentation accuracy against implementation using git forensics and code analysis with file paths, li
Related Skills
Wiki Backfill
Backfill a retroactive project history page — mines merged PRs, git log, tags, wrap logs, and ADRs into an app
Grep Jsonl
Inspect Mori's ~/.mori/logs/mori-YYYY-MM-DD.jsonl event log to diagnose user-reported issues — find errors, tr
Audit Burden
Find features carrying technical cost, architectural weight, or delivery constraints disproportionate to their