mcpField
E
explore-codebase

explore-codebase

github.com/tirth8205Development32.5k1.2k installsUpdated 2w ago
Repository

About explore-codebase

A codebase exploration skill that uses the code-review-graph to locate modules, symbols, and execution paths. It is intended for developers navigating unfamiliar code while keeping graph queries focused.

Key features

  1. 01Architecture and module exploration
  2. 02Semantic search for functions and classes
  3. 03Dependency relationship tracing
  4. 04Execution flow inspection
  5. 05Large-function discovery

Use cases

  1. 01Finding a function by name or keyword
  2. 02Tracing callers, callees, and imports
  3. 03Following a code execution path

MCP support

Uses code-review-graph MCP tools to inspect architecture, search code symbols, trace relationships, and explore flows.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tirth8205/code-review-graph --skill explore-codebase

After installing, type/explore-codebasein Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported