Explore codebase

Finish with Proof: a portable execution protocol for coding agents—diagnose before patching, bound delegation, and verify real outcomes.

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.

Copied from the file, not written here

Navigate and understand codebase structure using the knowledge graph

1.2 KB, as published. Nobody here has run it

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

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.

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.