understanding-code-archaeology

Reconstruct historical decisions from git history, commits, PRs, and issues to understand why code became the way it is rather than how it should ideally be. Use when: (1) code appears unnecessarily complex or inconsistent with surrounding patterns without obvious reason, (2) about to refactor or remove code that seems unnecessary without knowing what problem it originally solved, (3) encountering workarounds or technical debt without knowing if the original constraint still applies, (4) proposals to change code rest on ideal design rather than evidence about what decisions were made and why

// tip: Run this command in your terminal to install the skill