Code-review-graph Explore Codebase

Name: Explore Codebase
Author: tirth8205

Navigate and understand codebase structure using the knowledge graph

install

source · Clone the upstream repo

git clone https://github.com/tirth8205/code-review-graph

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/tirth8205/code-review-graph "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/explore-codebase" ~/.claude/skills/tirth8205-code-review-graph-explore-codebase && rm -rf "$T"

manifest: skills/explore-codebase/SKILL.md

source content

Explore Codebase

Use the code-review-graph MCP tools to explore and understand the codebase.

Steps

Run
```
list_graph_stats
```
to see overall codebase metrics.
Run
```
get_architecture_overview
```
for high-level community structure.
Use
```
list_communities
```
to find major modules, then
```
get_community
```
for details.
Use
```
semantic_search_nodes
```
to find specific functions or classes.
Use
```
query_graph
```
with patterns like
```
callers_of
```
,
```
callees_of
```
,
```
imports_of
```
to trace relationships.
Use
```
list_flows
```
and
```
get_flow
```
to understand execution paths.

Tips

Start broad (stats, architecture) then narrow down to specific areas.
Use
```
children_of
```
on a file to see all its functions and classes.
Use
```
find_large_functions
```
to identify complex code.

Token Efficiency Rules

ALWAYS start with
```
get_minimal_context(task="<your task>")
```
before any other graph tool.
Use
```
detail_level="minimal"
```
on all calls. Only escalate to "standard" when minimal is insufficient.
Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.