why
Explain why code is shaped the way it is: design rationale, tradeoffs, regressions, data-backed thresholds. Searches git history, GitHub pull requests and issues, and any other evidence source available in the session in parallel, then returns a cited, confidence-tiered answer. Use how for runtime behavior.
Pinned to revision 17bf3b44c1c4, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/why/SKILL.md
- skills/why/references/epistemics.md
- skills/why/references/investigator-prompt.md
- skills/why/references/source-playbook.md
- skills/why/references/sources/code-archaeology.md
- skills/why/references/synthesizer-prompt.md
Every link opens the file at its source, pinned to the revision this page describes.