why

Code archaeology — recover the full history and *intent* behind a specific piece of code: what it does, the commit that first introduced it, the most recent significant change, the PR(s) those commits merged in, and the discussion around them in PR reviews, linked tickets (GitHub Issues, Linear, Jira, etc.), and team chat. Use this whenever the user asks WHY a piece of code exists, the HISTORY or reasoning behind a decision, "who wrote this and why", "what's the context here", or "what was this change for". ALSO invoke it proactively, before editing code, whenever you are about to make a non-trivial change to code that is unfamiliar, legacy, fragile, or whose intent is unclear — understanding the original reasoning prevents reintroducing bugs that an earlier change deliberately fixed. Also use it when reviewing someone else's change under those same conditions. Triggers on: git blame, code archaeology, "why is this here", "why was this done this way", tracing a regression to its origin, and understanding lega