Explore codebase
Navigate and understand codebase structure using the knowledge graphFrom its SKILL.md
npx -y skills add MiaoY0uShan/FP --skill explore-codebaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 8 commands, including `list_graph_stats` and 7 more.
SKILL.md
1.2 KB, 260 tokens by cl100k_base, as published. Nobody here has run it
Explore Codebase
Use the code-review-graph MCP tools to explore and understand the codebase.
Steps
- Run
list_graph_statsto see overall codebase metrics. - Run
get_architecture_overview_toolfor high-level community structure. - Use
list_communities_toolto find major modules, thenget_communityfor 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_flowsandget_flowto 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_functionsto 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.