A skill in Shubhamsaboo/awesome-llm-apps · 145,077 stars on GitHub
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite, refactor, or risky edit. Runs entirely locally.
Security grade of this SKILL.md: SAFE · how we grade
npx skills add Shubhamsaboo/awesome-llm-apps --skill commit-archaeologist -a claude-code
The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.
git blame names the last person to touch a line. This skill reconstructs the reason the line exists. It traces a file or current line range through local git history, identifies its origin and later edits, finds files that repeatedly changed beside it, and extracts intent clues from commit messages. Everything runs locally. No network calls, API keys, or repository writes. The user asks why a block, function, or file exists. The user wants to know who introduced code and what changed afterward. A rewrite or refactor needs historical constraints and change risks. A workaround, temporary branch, or surprising design choice needs context. The user only wants raw blame output or a commit list. The task is to squash, delete, or rewrite git history. The repository is remote and has not been cloned locally. The question is about project-wide architecture rather than one file or region.