explore-codebase

Installation
SKILL.md

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. Pass include_source=True, expand_neighbors=True to get the code of the hits and their direct callers and callees, so you need not open the files. Leave detail_level at its default for this call: minimal drops the source.
  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, and path_to with to shows how one symbol reaches another.
  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" unless it is not enough. Minimal drops source, so leave semantic_search_nodes_tool(include_source=True) and get_review_context_tool at standard.
  • Prefer a targeted query_graph_tool call over a broad listing call.
  • Budget: about five tool calls per task. Source snippets stand in for file reads.
  • Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.
Installs
410
GitHub Stars
32.9K
First Seen
Jul 17, 2026