Code Archeologist Analysis

Research the history of the code to understand why decisions were made and identify hidden constraints.

Analysis Checklist

Git History Analysis

• Run git blame on target files to identify authors and change dates
• Review commit messages for rationale behind key decisions
• Trace the evolution of critical functions through git log
• Identify code that has been frequently modified (churn analysis)

Decision Rationale

• Extract reasoning from commit messages and PR descriptions
• Check for linked issues or tickets explaining requirements
• Identify comments that document "why" rather than "what"
• Look for TODO/FIXME/HACK comments with historical context