MCP server that gives Claude Code the rationale behind a symbol before editing - synthesized from git history, PRs, and call-graph context.
Cursor rule
When the user asks "why does X exist?", "what is X for?", "is X still needed?", "can I delete X?", or any similar intent-question about an existing code symbol, call the whygraphrationalebrief MCP tool and surface its output verbatim. Read-only — don't paraphrase or pre-answer.
Cursor rule
Always-on guidance for using the CodeGraph (codegraph) MCP tools. Prefer them over grep for structural questions; don't pull large explore output into context; trust their AST-parsed results.
Cursor rule
When the user has a reviewed WhyGraph plan markdown file and wants to execute it — "implement that plan", "execute the plan at ", "run through the steps", "carry out the plan", "let's apply the plan" — surface the /whygraph-implement slash command. Cost-gated — don't run /whygraph-implement automatically; the user…
Cursor rule
When the user wants to plan a non-trivial code change — "plan how to add X", "what would it take to migrate to Y", "outline the steps to refactor Z" — surface the /whygraph-plan slash command. The planner grounds the plan in CodeGraph (structural impact) and WhyGraph (rationale, constraints, risks). Cost-gated — don't…
Cursor rule
Before editing, refactoring, renaming, deleting, or replacing existing code, call the whygraphrationalebrief MCP tool to learn the intent, constraints, tradeoffs, and risks behind it. Skip for new code, typos, or formatter-only changes.