Agent skill · software engineering · shubhamsaboo
commit-archaeologist
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.
Why this skill is useful
Adds a specialized script for analyzing git history to reconstruct code intent, which the AI wouldn't reliably generate on its own.
What it needs
Requires python3 installed locally. About 3k tokens when loaded. Last updated 2026-08-03. 131,141 stars on the source repository.
What this skill does
Commit Archaeologist 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. When to use 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 When not to use 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 Gather the target Get the repository path and tracked file path. Use a line range when the user names a current block or function. If either path is missing, ask only for the missing value. Do not scan sibling repositories. Paths should be relative to the repository and use forward slashes. Line ranges use inclusive current line numbers such as 40-72. Run the dig From this skill directory: For the complete history of a file, omit --lines: The script is read-only. With a range it uses git line-log; without one it uses file history with rename following. It also reads current authorship with blame. If it rejects a path or range, report that error and ask for a corrected target. Before interpreting the JSON, read references/reading-git-history.md. Its confidence rules prevent blame ownership, correlation, and commit-message hints from becoming false certainty. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills shubhamsaboo/commit-archaeologist