Investigates design rationale behind code by querying git history, tickets, docs, chat, and observability sources in parallel.
npx skills add https://github.com/petemcw/farseer --skill but-why-petemcw
Please help me install this Agent Skill. Skill: but-why Source: https://github.com/petemcw/farseer/tree/main/skills/but-why Command: npx skills add https://github.com/petemcw/farseer --skill but-why-petemcw
High-intent search queries and answers about installing and using this skill.
Ask a why question about the target code and the skill anchors it via git blame and log, then spawns parallel investigators across source control, tickets, docs, chat, and monitoring tools. A synthesizer returns a cited answer with confidence tiers.
but-how explains what the code does and how it works at runtime. but-why explains the forces that led to its shape, using historical evidence from commits, PRs, tickets, docs, and conversations.
Git and the gh CLI are always used for source control history. Optional MCP categories include Jira or Linear for tickets, Confluence or Notion for docs, Slack for chat, Datadog for observability, Sentry for errors, and Snowflake or BigQuery for analytics.
The skill reports an explicit Unknown rather than guessing. It documents exactly which sources and queries were searched, what returned nothing, and which people would likely know the answer.
Yes. After the evidence report, the skill converts lineage findings into a Preserve, Change, Avoid, and Risk constraint set suitable for planning modifications without breaking the original intent.
rockcookiesInvestigate design rationale behind code by querying git history and MCP evidence sources.
JhonMA82Creates implementation plans and executes tasks for Comet workflow build phases.
patsnapExplain materials science and engineering technologies with structure-property analysis.
udecodeCreate and update GitHub draft pull requests with conventional commits.
