Commit Archaeologist 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…