gitnexus-guide

GitNexus provides tools including query for execution flows, context for symbol views, impact for blast radius, trace for shortest paths between symbols, rename for multi-file renames, cypher for raw graph queries, and route_map for API endpoint mapping.

Use the impact tool, which computes a symbol's blast radius showing what breaks at depth 1, 2, and 3 with confidence scores. For current uncommitted changes, use detect_changes to see what your git diff affects.

Use the trace tool with from and to symbol names to get the shortest directed path over CALLS edges in one call. It returns ordered hops with file paths and line numbers, and reports the furthest reachable node when no path exists.

Yes, the explain tool returns taint findings recorded by running gitnexus analyze with the --pdg flag, covering sink categories like command-injection, sql-injection, and xss. Repos indexed without --pdg return a note that no taint layer exists.

Read the gitnexus://repo/{name}/schema resource first, since it is the authoritative schema for the indexed repo. Then use the cypher tool with CodeRelation edge types like CALLS, IMPORTS, or EXTENDS to match nodes such as Function, Class, and File.

Taint analysis does not model closure/callback, property/field, or implicit flows, and interprocedural findings are function-level hops rather than statement-level proof. The absence of a finding is not proof of safety.