why
Investigate why code has its current shape with /why. Use for design rationale, regressions, postmortems, and data-backed thresholds. Discovers MCP tools, maps each to one of seven evidence categories, runs investigators, and returns a cited answer that separates facts from inference.
- License
- Apache-2.0
Pinned to revision 654e32410e5f, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/why/SKILL.md
- skills/why/CHANGELOG.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.