---
name: Explore Codebase
slug: explore-codebase
category: Quality
description: Explore Codebase uses knowledge graph tools to navigate and understand codebase structure, trace relationships, and find execution paths. Use it for code review, debugging, and refactoring with minimal context.
github: "https://github.com/tirth8205/code-review-graph/tree/main/skills/explore-codebase"
language: Python
stars: 30048
forks: 2760
install: "npx degit https://github.com/tirth8205/code-review-graph/tree/main/skills/explore-codebase ~/.claude/skills/explore-codebase"
installs_to: ~/.claude/skills/explore-codebase
source_path: skills/explore-codebase/SKILL.md
collection_size: 7
category_size: 1354
collection_url: "https://dirskills.com/collections/tirth8205/code-review-graph"
added: 2026-08-14T07:11:47.912Z
last_synced: 2026-08-14T07:11:47.912Z
canonical_url: "https://dirskills.com/skills/explore-codebase"
---

# Explore Codebase

Explore Codebase uses knowledge graph tools to navigate and understand codebase structure, trace relationships, and find execution paths. Use it for code review, debugging, and refactoring with minimal context.

**Install:**

```bash
npx degit https://github.com/tirth8205/code-review-graph/tree/main/skills/explore-codebase ~/.claude/skills/explore-codebase
```

## README

## 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_tool` for high-level community structure.
3. Use `list_communities_tool` to find major modules, then `get_community` for details.
4. Use `semantic_search_nodes_tool` to find specific functions or classes.
5. Use `query_graph_tool` 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.