explore-codebase
Installation
SKILL.md
Explore Codebase
Use the code-review-graph MCP tools to find your way around the codebase.
Steps
- Call
get_architecture_overview_toolfor the community structure. Calllist_communities_tool, thenget_community_tool, only for the modules you need. - Call
semantic_search_nodes_toolto find a function or class by name or keyword. Passinclude_source=True, expand_neighbors=Trueto get the code of the hits and their direct callers and callees, so you need not open the files. Leavedetail_levelat its default for this call:minimaldrops the source. - Call
query_graph_toolwithcallers_of,callees_oforimports_ofto trace relationships.children_ofon a file lists its functions and classes, andpath_towithtoshows how one symbol reaches another. - Call
list_flows_tool, thenget_flow_toolfor one flow, to follow an execution path. - Call
find_large_functions_toolto find oversized functions. - Call
list_graph_stats_toolonly 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 leavesemantic_search_nodes_tool(include_source=True)andget_review_context_toolat standard. - Prefer a targeted
query_graph_toolcall 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.