code-archaeology

Compound V — a multi-model orchestrator for Claude Code, layered on Superpowers: a deterministic router (Opus for risky work, Sonnet for the mechanical), cross-model review (Claude + Codex), 3 scouts (code · docs · domain), semantic memory, and Epic/Marathon autonomous loop mode. The pill that turns one freelancer into a squad.

Codex skill for evidence-backed code archaeology from local git history

处女作 · 微信公众号爬虫（Playwright + Python）

Quill — ISA Spec Architect & Code Archaeologist | Bootable fleet agent twin with lighthouse keeper integration

AI-powered git history explainer - understand why code exists

Claude Code skill that investigates Chesterton's fence — point it at a weird line of code and it digs through blame, old commits, and PR archaeology to answer: why does this exist, and is it safe to delete? 🚧

🔍 dig — generate a self-contained HTML code-archaeology report from any git repo. Single static Go binary, zero deps, beautiful output.

MCP Silex

git blame for WHY, not who — a Claude Code skill that recovers the intent behind a line of code and refuses to invent one. The recover-side companion to git-why.

Turn local Git history into a private, evidence-backed documentary you can replay, investigate, compare, and present.

Evidence-first code archaeology for Git history, pull requests, issues, reviews, and reverts.

git 이력을 추적해 '이 코드 지워도 되나'에 커밋 근거로 답하는 Claude Code 스킬. 포매터·스쿼시·코드 이동 노이즈를 넘어 진짜 도입 커밋을 찾습니다.

Read-only, structured access to a Git repository's history — as an MCP server and a CLI. Hardened against option injection and hostile repo config.

Git archaeology for AI coding agents: distill a repo's full history into durable engineering memory (.repo-memory/).

Why is this code like this? A local-first CLI that reconstructs the intent behind a line of code from its git history — sourced, and it refuses to make things up.

Preserving, mining, and modernizing PHYLIP's algorithmic legacy — 35,805 lines of Rust, 1,050 tests, zero dependencies

An AI-powered RAG tool that turns Git history into a searchable knowledge base to uncover the 'why' behind your code.

Point Claude Code at an unfamiliar codebase and get back, in minutes, the map that usually takes weeks of pairing: real entry points, core vs. peripheral modules, and buried historical workarounds.

git blame that answers *why*, not just *who* — line-level git archaeology with no network and no configuration

CLI that shows why a file exists - git history, growth over time, and who actually imports it.