GitNexus Explore

CLI ONLY — no MCP server exists. Never use readMcpResource with gitnexus:// URIs.

Trace execution flows and understand how code works using the GitNexus knowledge graph.

When to Use

• "How does X work?"

• "What's the execution flow for Y?"

• "Walk me through the Z subsystem"

• Exploring unfamiliar code areas before making changes

Workflow

Step 0: Pre-flight — Ensure CLI Is Callable

The gitnexus binary is installed via npm/mise. The mise shim may fail if node isn't active in the current project. Run this pre-flight before any gitnexus command:

Test if gitnexus is actually callable (not just a broken shim)

gitnexus --version 2>/dev/null || mise use node@25.8.0

All commands below run from the repo root. If multiple repos are indexed in the workspace, add --repo <repo-name> to specify the target. Otherwise --repo is optional.

Step 1: Auto-Reindex If Stale

gitnexus status

If stale (indexed commit ≠ HEAD), automatically reindex before proceeding — do not ask the user:

gitnexus analyze

Then re-check status to confirm index is current.

Step 2: Find Execution Flows

gitnexus query "<concept>" --limit 5

This returns ranked execution flows (process chains) related to the concept.

Step 3: Get 360° Symbol View

For each relevant symbol found:

gitnexus context "<symbol>" --content

This shows:

• Callers — who calls this symbol

• Callees — what this symbol calls

• Processes — execution flows this symbol participates in

• Source — the actual code (with --content )

If multiple candidates are returned, disambiguate with:

gitnexus context "<symbol>" --uid "<full-uid>" --content

or

gitnexus context "<symbol>" --file "<file-path>" --content

Step 4: Read Source Files

Use the Read tool to examine source files at the line numbers identified by GitNexus.

Step 5: Synthesize

Present a clear explanation covering:

• What it is — purpose and responsibility

• Execution flows — how data moves through the system

• Dependencies — what it depends on, what depends on it

• Key files — the most important files to understand

Example

User: "How does the kintsugi gap repair work?"

gitnexus query "kintsugi gap repair" --limit 5 gitnexus context "KintsugiReconciler" --content gitnexus context "discover_shards" --content

Then read the relevant source files and synthesize the explanation.