why
Explain why code or a design has its current shape using repository history and directly observable evidence.
Pinned to revision cb10d1cac799, 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.