explain-why
Find out why code or infrastructure is the way it is (a design choice, a threshold, a workaround, or a regression) from git history, GitHub PRs and issues, ADRs, phase docs, CHANGELOG, CLAUDE.md/AGENTS.md, and memory, and report each claim at a stated confidence (found, inferred, unknown) with a citation. Read-only. A Sonnet digger works the git and PR history. Before a change, it ends with a Preserve / Change / Avoid / Risk set. Triggers on "/explain-why", "why does X work this way", "why did we pick Y", "where did this number come from", or "is it safe to remove this". Optional leading level. Use explain-how for runtime behavior.
Target: Design & content creation. Automatically collected · unverified.
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: harrison-wallace/ai-engineering · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T19:02:12.526Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
License unknown. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.