Come usare
- Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
- Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
- Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/tirth8205/code-review-graph --skill explore-codebasePrima di iniziare
- L’installazione non include abbonamenti, quote API o accesso ai file.
- Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.
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.


