- Check index readiness with
codegraph_statusand, when relevant,list_repos. - Use
codegraph_searchor GitNexusqueryto find candidate symbols or flows. - Use
codegraph_contextor GitNexuscontexton the best candidate. - Read source files only for the final verification pass.
- Start with
get_minimal_context_tool. - Run
detect_changes_tool. - Use
get_review_context_toolfor focused review context. - Use
get_impact_radius_toolfor risky changes. - If flow-level understanding is needed, use GitNexus
detect_changes,query, orcontext. - Read only the files implicated by the graph output.
- Start with
get_minimal_context_toolif the bug surface is broad. - Search by symptom using GitNexus
query. - Inspect suspect symbols with
codegraph_contextand GitNexuscontext. - Use
codegraph_callers/codegraph_calleesorquery_graph_toolto trace data and control flow. - If execution-flow context matters, inspect GitNexus process resources.
- Confirm root cause with direct source reads.
- Identify the target symbol with
codegraph_searchor GitNexusquery. - Run GitNexus
impactand/orcodegraph_impactbefore editing. - Use
codegraph_callers/codegraph_calleesandquery_graph_toolto map dependencies. - For renames, use GitNexus
renamewith dry-run first. - After edits, run GitNexus
detect_changes. - Then read and validate the exact touched files.
- Start with GitNexus
list_repos. - If repos are grouped, use
group_list,group_status, andgroup_query. - Narrow to the specific repo or flow before using repo-local tools from codegraph or code-review-graph.