gitnexus-guide

GitNexus provides seven MCP tools: query for process-grouped code intelligence, context for 360-degree symbol views, impact for blast radius analysis, detect_changes for git-diff impact, rename for multi-file renames, cypher for raw graph queries, and list_repos for discovering indexed repositories.

Run npx gitnexus status and compare the indexed commit to git rev-parse HEAD; if they differ, run npx gitnexus analyze. Note that the status command exits 0 in every case, so parse stdout rather than branching on the exit code.

Read the gitnexus://repo/{name}/schema resource first to learn the node types (File, Function, Class, Interface, Method, Community, Process) and edge types (CALLS, IMPORTS, EXTENDS, IMPLEMENTS, DEFINES, MEMBER_OF, STEP_IN_PROCESS), then use the cypher tool with CodeRelation type filters.

On a stale index, detect_changes returns "No changes detected." regardless of actual modifications, meaning it has no information rather than confirming safety. Re-index with npx gitnexus analyze before relying on its output.

The staleness warning fails open: an indexed commit that was rebased away or garbage-collected reads as fresh, and uncommitted changes are never detected. Absence of a warning is not an all-clear, so verify the indexed commit against HEAD manually.