Investigate design rationale behind code by querying git history and MCP evidence sources in parallel.
npx skills add https://github.com/edivad1999/stuc-stack --skill why-edivad1999
Please help me install this Agent Skill. Skill: why Source: https://github.com/edivad1999/stuc-stack/tree/main/skills/why Command: npx skills add https://github.com/edivad1999/stuc-stack --skill why-edivad1999
High-intent search queries and answers about installing and using this skill.
Anchor the investigation with git blame and git log on the target lines, then pull PR bodies via gh or glab. This Skill automates that and fans out parallel investigators across tickets, docs, chat, and telemetry to gather cited evidence.
The how skill explains what the code does and how it works at runtime. The why skill explains the forces that led to its shape: design rationale, tradeoffs, incidents, and external constraints found in the historical record.
Yes, but with reduced coverage. Source control investigation via git and gh always runs; other categories like Slack, Notion, Linear, Datadog, Sentry, or Databricks require matching MCP servers, and missing ones are documented as gaps.
It reports an explicit Unknown tier, listing exactly which sources were searched, which queries ran, and what returned nothing. Gaps are named concretely rather than filled with plausible-sounding guesses.
Yes. When the target looks defensive, investigators also apply a cross-cutting incident-postmortem playbook, hunting for outage history, Sentry error spikes, and postmortem action items that motivated the code.
ShtianInvestigate design rationale behind code by querying git history and MCP evidence sources in parallel.
fernandoxavier02Verify code-review feedback against codebase scope and constraints before implementing.
petemcwExplains how code works and why it was built that way in plain language.
rockcookiesTrace when code was introduced, removed, or modified using git pickaxe, blame, and bisect.
