Code Archaeology (git + in-repo)
Code Archaeology (git + in-repo)
Section titled “Code Archaeology (git + in-repo)”What this source contains
Section titled “What this source contains”- Commit history (messages, dates, authors, diffs)
- PR descriptions, review comments, and discussion threads (via
gh) - Inline code comments, TODOs, FIXMEs, deprecation notes
- ADRs (architectural decision records) if the repo keeps them
- Tests, whose names and assertions often encode the edge cases that motivated a change
- Related files modified in the same commits (co-change signal)
- CHANGELOG entries and release notes in the repo
- Issue/ticket IDs in commit messages and PR bodies
The most trustworthy source, tied directly to the code, and the most complete. Everything that went through the repo should be here.
How to search it
Section titled “How to search it”Expand the seed commit list:
# History through renamesgit log --follow --oneline -- <file>
# Pickaxe: commits that added or removed this exact textgit log -S '<exact_string_from_code>' -- <file>
# Or for patterns:git log -G '<regex>' -- <file>
# Who wrote each line and whengit blame -L <start>,<end> <file>
# One commit's full diffgit show <hash>
# Commits between two points affecting this filegit log <old>..<new> -p -- <file>Look for out-of-band docs:
# ADRs often live in docs/adr/ or similarrg -l -i 'architecture.decision' --glob '*.md'
# TODOs and FIXMEs near the targetrg -n -C2 '(TODO|FIXME|HACK|XXX|NOTE)' <target_file>
# Related testsrg -l '<symbol>' --glob '*test*'