Explore Codebase Use the code review graph MCP tools to find your way around the codebase. Steps 1. Call get architecture overview tool for the community structure. Call list communities tool , then get community tool , only for the modules you need. 2. Call semantic search nodes tool to find a function or class by name or keyword. 3. Call query graph tool with callers of , callees of or imports of to trace relationships. children of on a file lists its functions and classes. 4. Call list flows tool , then get flow tool for one flow, to follow an execution path. 5. Call find large functions tool to find oversized functions. 6. Call list graph stats tool only when you need node, edge and language counts. Token Efficiency Rules Call get minimal context tool(task="<your task ") before any other graph tool. Pass detail level="minimal" wherever a tool accepts it. Use "standard" only when minimal is not enough. Prefer a targeted query graph tool call over a broad listing call. Budget: about five tool calls and 800 tokens of graph output per task. Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.

explore-codebase