tirth8205/code-review-graph

explore-codebase

Navigate and understand codebase structure using the knowledge graph

First seen Jul 17, 2026
8-week activity · all time api

Installation

$ npx skills add tirth8205/code-review-graph --skill explore-codebase

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from tirth8205/code-review-graph.

npx skills add tirth8205/code-review-graph

Browse all from tirth8205/code-review-graph

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 31.3K
License LICENSE
Default branch main
Open issues 88
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,364 B
  • docs SUMMARY.md 1,337 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1,100 installs

SKILL.md

Explore Codebase

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

Steps

  1. Run listgraphstats_tool to see overall codebase metrics.
  2. Run getarchitectureoverview_tool for high-level community structure.
  3. Use listcommunitiestool to find major modules, then getcommunitytool for details.
  4. Use semanticsearchnodes_tool to find specific functions or classes.
  5. Use querygraphtool with patterns like callersof, calleesof, imports_of to trace relationships.
  6. Use listflowstool and getflowtool 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 findlargefunctions_tool to identify complex code.

Token Efficiency Rules

  • Start with getminimalcontext_tool(task="<your task>") before other graph tools.
  • 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.
  • Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.