why - Investigate the motivation and intent behind code.
Answer why code works a certain way by querying history sources in parallel and returning a confidence-weighted analysis of decisions and tradeoffs.
Tags
Updated: 2026-09-21Capabilities
Typical Inputs
Typical Outputs
What this skill does
- Anchor target code in git history
- Spawn parallel investigators for evidence sources
- Query git log and pull requests
- Synthesize findings using epistemics framework
- Generate change constraints from lineage findings
Inputs
- Target file paths and line ranges
- User design rationale question
- Available MCP servers and tools
- Reference playbook and framework files
Outputs
- Confidence-weighted rationale synthesis report
- Consulted sources log with justifications
- Code change constraint set
Requirements
- git CLI tool
- gh CLI tool
- MCP servers for evidence sources
- Reference files in references directory