Explore codebase

Skill MiaoY0uShan/FP/.gemini/skills/explore-codebase

Navigate and understand codebase structure using the knowledge graphFrom its SKILL.md

Install

npx -y skills add MiaoY0uShan/FP --skill explore-codebase

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 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.

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_stats to see overall codebase metrics.
Run get_architecture_overview_tool for high-level community structure.
Use list_communities_tool to find major modules, then get_community for details.
Use semantic_search_nodes_tool to find specific functions or classes.
Use query_graph_tool with patterns like callers_of, callees_of, imports_of to trace relationships.
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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most architecture codebase skills give in 260 tokens

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07

Ask the user which candidate to explorein 45 of 811, across 15 files
Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
Read any relevant architecture decision records firstin 31 of 811, across 8 files
Use exact glossary terms in every suggestionin 30 of 811, across 10 files
Accept dependencies instead of creating themin 24 of 811, across 5 files
Include before and after visualisations for each candidatein 24 of 811, across 5 files
Read the domain glossary before exploringin 24 of 811, across 6 files
Return results instead of producing side effectsin 23 of 811, across 4 files
Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
Introduce seams only where things varyin 22 of 811, across 3 files
Reduce the number of methodsin 21 of 811, across 2 files
Design deep modules with small interfacesin 21 of 811, across 3 files

Said here and by no other author read

start with get_minimal_context before any other graph tool
use detail_level minimal on all calls
escalate to detail_level standard only when minimal is insufficient
complete any task in at most five tool calls
limit total output tokens to 800 or less
run list_graph_stats to see codebase metrics

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.