get_why
Retrieves architectural decisions and evidence commits behind code. Query by question, file path, or get a decision health dashboard. Falls back to git archaeology for undocumented paths.
Instructions
Why this code is shaped this way — decision records + evidence commits.
Call before refactors or pattern divergences. Query modes: a question
("why is auth using JWT?"), a file path (governing decisions + origin
story + alignment score), a question anchored to targets, or no query
(decision health dashboard). Falls back to git archaeology when no
decisions exist for a path — never empty.
Args:
query: question, file/module path, or omit for the dashboard.
targets: optional file paths to anchor the search.
repo: usually omitted.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| repo | No | ||
| query | No | ||
| targets | No |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |