gitnexus-guide

Use the impact tool, which reports a symbol's blast radius at depths 1, 2, and 3 with confidence scores. For changes already in your working tree, detect_changes analyzes the git diff to show what your current edits affect.

GitNexus provides query, context, impact, trace, detect_changes, rename, cypher, explain, pdg_query, check, route_map, shape_check, api_impact, tool_map, group_list, group_sync, and list_repos. Each covers a specific code intelligence task from execution flows to API route mapping.

Use the trace tool with from and to symbol names to get the shortest directed path over CALLS and HAS_METHOD edges. Disambiguate common names with from_uid/to_uid or file filters, and bound the search with maxDepth up to 30.

Yes, the explain tool returns source-to-sink taint findings recorded by running analyze with the --pdg flag, covering categories like command injection, SQL injection, and XSS. Repositories indexed without --pdg return a note that no taint layer exists.

list_repos is paginated with a default limit of 50 and a maximum of 200 per call. Keep calling it with offset set to the returned nextOffset until hasMore is false to enumerate every repository.

Read the gitnexus://repo/{name}/schema resource first, since it is the authoritative schema for the indexed repo. It lists node types like Function, Class, and Route plus edge types such as CALLS, IMPORTS, and HANDLES_ROUTE.