commit-archaeologist

Run the archaeologist script with the repository path, file path, and optional line range to trace the introducing commit and later changes. It uses git line-log for ranges and git log --follow for whole files, producing a JSON report with timeline, authorship, and intent signals.

Pass a line range like --lines 40-72 to the script, which uses git line-log to follow only the commits that shaped those current lines. The oldest commit in that timeline is the region's introduction, which may differ from the file's first commit.

No, everything runs locally using Python's standard library and git commands. The script is read-only, makes no network calls, and requires no API keys or repository writes.

Blame only shows who last modified surviving lines, not the original author. The report keeps current blamed-line counts separate from historical commit counts so you can distinguish recent editors from the introducing author.

Commit message categories are keyword heuristics, not verified intent, and co-change patterns show correlation rather than proven dependencies. Sparse history, generic messages, or bulk rewrites lower confidence, so conclusions beyond the evidence should be labeled as inference.