gitnexus-guide

GitNexus provides query, context, impact, trace, detect_changes, rename, cypher, explain, pdg_query, check, and list_repos tools. Each serves a distinct purpose, from execution-flow grouping to blast-radius analysis and raw Cypher graph queries.

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.

Call list_repos with limit (max 200, default 50) and offset, then keep paging using pagination.nextOffset until hasMore is false. Ordering is deterministic by lower-cased name then path, so paging never skips or duplicates entries.

No. Taint findings from explain are intra-procedural only, so cross-function, closure, property, and implicit flows are not modeled. Absence of a finding is not proof of safety, and repos indexed without --pdg have no taint layer at all.

explain returns persisted source-to-sink taint findings with sink categories like sql-injection and xss. pdg_query reads control-dependence (controls mode) and reaching-definition data-flow (flows mode) edges, always anchored to a target file or symbol.

Read the gitnexus://repo/{name}/schema resource first, then use the cypher tool. Nodes include File, Function, Class, and Method; relationships use CodeRelation types such as CALLS, IMPORTS, EXTENDS, and DEFINES.