Explore Codebase
- Repo stars 17,985
- Author repo code-review-graph
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tirth8205 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
## Explore Codebase
Use the code-review-graph MCP tools to explore and understand the codebase.
### Steps
1. Run `list_graph_stats` to see overall codebase metrics.
2. Run `get_architecture_overview` for high-level community structure.
3. Use `list_communities` to find major modules, then `get_community` for details.
4. Use `semantic_search_nodes` to find specific functions or classes.
5. Use `query_graph` with patterns like `callers_of`, `callees_of`, `imports_of` to trace relationships.
6. 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.
Sections and files
Listed in source order.
sections -> Explore Codebase → Steps → Tips → Token Efficiency Rules
terms -> Use the code-review-graph MCP tools to explore and understand the codebase. · 1. Run listgraphstats to see overall codebase metrics. · - Start broad (stats, architecture) then narrow down to specific areas.
files/cmd -> list_graph_stats · get_architecture_overview · list_communities · get_community · semantic_search_nodes · query_graph · callers_of · callees_of
body sha256 -> 64420a56b8c9
Steps
Run
list_graph_statsto see overall codebase metrics. Runget_architecture_overviewfor high-level community structure. Uselist_communitiesto find major modules, thenget_communityfor details. Usesemantic_search_nodesto find specific functions or classes. Usequery_graphwith patterns likecallers_of,callees_of,imports_ofto trace relationships.Tips
Start broad (stats, architecture) then narrow down to specific areas. Use
children_ofon a file to see all its functions and classes. Usefind_large_functionsto identify complex code.Token Efficiency Rules
ALWAYS start with
get_minimal_context(task="<your task>")before any other graph tool. Usedetail_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.