Explore an unfamiliar codebase using a graph of code relationships. Inspect its structure, find functions and classes, trace calls and imports, follow execution paths, and locate large functions for closer investigation.
Navigate and understand codebase structure using the knowledge graph
Review the instructions the agent will receive before you install.
Use the code-review-graph MCP tools to find your way around the codebase.
get_architecture_overview_tool for the community structure. Call list_communities_tool, then get_community_tool, only for the modules you need.semantic_search_nodes_tool to find a function or class by name or keyword.query_graph_tool with callers_of, callees_of or imports_of to trace relationships. children_of on a file lists its functions and classes.list_flows_tool, then get_flow_tool for one flow, to follow an execution path.find_large_functions_tool to find oversized functions.list_graph_stats_tool only when you need node, edge and language counts.get_minimal_context_tool(task="<your task>") before any other graph tool.detail_level="minimal" wherever a tool accepts it. Use "standard" only when minimal is not enough.query_graph_tool call over a broad listing call.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Build or refresh a knowledge graph, a map of code relationships used for code review. Choose a full rebuild or an incremental update, then report the operation's status and summary.
Investigate bugs using a graph of code relationships. Find relevant functions, trace calls and execution paths, check recent changes, and assess what a proposed fix could affect before reading and changing the implementation.
Plan refactoring with dependency analysis, which shows how code parts rely on each other. Find candidates and unreferenced code, preview and apply renames, and compare the resulting impact with the original plan.
Review code changes using a knowledge graph, a map of code relationships, to assess risk and affected behavior. Organize findings by severity, identify missing tests, suggest fixes, and provide a merge recommendation.
Review code changes against the previous commit and identify affected files and functions. Use dependency relationships to assess risk, check missing tests, and produce a focused report with issues and recommendations.
Review all changes in a pull request or branch against its base branch. Use a knowledge graph, a map of code relationships, to report affected files and functions, test coverage, API compatibility issues, and recommended actions.