Problem
Developers spend 20+ minutes understanding unfamiliar codebases. Existing tools measure metrics but none explain a codebase the way a senior developer would.
Proposed Solution
Build an MCP server + CLI that analyzes git history, code structure, naming patterns, and dependency graphs to reverse-engineer institutional knowledge.
MCP Server Tools
analyze_codebase — full codebase analysis with pattern detection
explain_decision — explain architectural decisions from git history
generate_claude_md — generate the CLAUDE.md that should have existed
map_tribal_knowledge — map undocumented conventions
CLI
archaeologist dig ./my-repo — full analysis report
Dependencies
- Python 3.12+, MCP SDK, Click, GitPython
Success Criteria
Tracking
Deep research BRIEF: ~/deep-research/active/codebase-archaeologist/BRIEF.md
Problem
Developers spend 20+ minutes understanding unfamiliar codebases. Existing tools measure metrics but none explain a codebase the way a senior developer would.
Proposed Solution
Build an MCP server + CLI that analyzes git history, code structure, naming patterns, and dependency graphs to reverse-engineer institutional knowledge.
MCP Server Tools
analyze_codebase— full codebase analysis with pattern detectionexplain_decision— explain architectural decisions from git historygenerate_claude_md— generate the CLAUDE.md that should have existedmap_tribal_knowledge— map undocumented conventionsCLI
archaeologist dig ./my-repo— full analysis reportDependencies
Success Criteria
Tracking
Deep research BRIEF:
~/deep-research/active/codebase-archaeologist/BRIEF.md