why
Find out why code is the way it is (design rationale, past decisions, regressions, where a threshold came from) by searching git, PRs and every connected ticket, doc, chat and observability tool in parallel, and return a cited, confidence-tiered answer. Use for "why does X work this way" or "why did we pick Y". Use how for what code does.
- Version
- 0.1.0
- License
- MIT
Pinned to revision 524e32ba9e15, 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/sources/databricks.md
- skills/why/references/sources/datadog.md
- skills/why/references/sources/incident-postmortem.md
- skills/why/references/sources/linear.md
- skills/why/references/sources/notion.md
- skills/why/references/sources/sentry.md
- skills/why/references/sources/slack.md
- skills/why/references/synthesizer-prompt.md
Every link opens the file at its source, pinned to the revision this page describes.