---
name: why
description: Explain why code or a design has its current shape using repository history and directly observable evidence.
---

# Why

Use this skill for design rationale, regressions, postmortems, tradeoffs, or questions about why a repository chose a behavior.

1. State the exact decision or behavior being explained and the evidence boundary.
2. Read the current code, callers, configuration, tests, and relevant `git log` or `git blame` history.
3. Separate facts from inferences. Mark missing evidence instead of filling the gap.
4. Explain the constraint, alternatives, decision, and consequence in plain language.
5. Cite the files, commits, or commands that support each important claim.

Do not claim an intent that the code, history, or repository evidence does not support.