Skip to content

Commit Archaeologist

Explains why a file or code block exists by reading its local git history

Stars
143,726
Licence
Apache-2.0
Files
4 files

What it does

When you ask why some code exists, the agent runs a bundled Python script that reads your local git history for that file or line range. It finds the commit that first introduced the code, the later edits, files that often changed alongside it, and clues in commit messages such as reverts, workarounds, and TODOs. It then writes a short report with a best-guess explanation and a confidence level, so you can check the context before a risky rewrite.

Great for

  • Developers about to refactor or rewrite code they did not write
  • Teams trying to recover the reason behind a workaround or odd design choice
  • Reviewers who need history context before approving a change to legacy code

Skip it if

  • Remote repositories that have not been cloned locally, since the script only reads local git data
  • Requests to squash, delete, or rewrite history, which the skill explicitly excludes
  • Project-wide architecture questions, because the skill focuses on one file or line range; commit messages may also be too vague to explain intent

Try asking

  • “Why does this function in src/cache.py exist? Explain its history.”
  • “Who wrote lines 40-72 of src/cache.py and why before I refactor it?”
  • “Explain the history of this workaround in the parser before I rewrite it.”
Step-by-step guide: how to use Commit ArchaeologistInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 4 original files, the Apache-2.0 licence and an attribution note.

    commit-archaeologist.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip commit-archaeologist.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip commit-archaeologist.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give a line range for a specific function so the report focuses on that block rather than the whole file's history.
  • Expect a low-confidence result when commit messages are vague; the skill is designed to say so rather than invent a rationale.
  • Treat co-changed files as coupling clues to verify, not confirmed dependencies.

What's inside

  • README.md
  • references/reading-git-history.md
  • scripts/archaeologist.py
  • SKILL.md

Redistributed unmodified from Shubhamsaboo/awesome-llm-apps under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.