How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/tirth8205/code-review-graph --skill explore-codebaseBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Explore Codebase
Use the code-review-graph MCP tools to explore and understand the codebase.
Steps
- Run
list_graph_stats_toolto see overall codebase metrics. - Run
get_architecture_overview_toolfor high-level community structure. - Use
list_communities_toolto find major modules, thenget_community_toolfor details. - Use
semantic_search_nodes_toolto find specific functions or classes. - Use
query_graph_toolwith patterns likecallers_of,callees_of,imports_ofto trace relationships. - Use
list_flows_toolandget_flow_toolto understand execution paths.
Tips
- Start broad (stats, architecture) then narrow down to specific areas.
- Use
children_ofon a file to see all its functions and classes. - Use
find_large_functions_toolto identify complex code.
Token Efficiency Rules
- Start with
get_minimal_context_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.
