Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

Exploring Codebases with GitNexus When to Use "How does authentication work?" "What's the project structure?" "Show me the main components" "Where is the database logic?" Understanding code you haven't seen before Bind the repository first Step 1 discovers what is indexed; every call after it must say which of those it means. With one indexed repository, use the examples below as written. With more than one, pass repo on every call: an omitted repo normally errors, but under an MCP policy with a configured default it resolves to that default silently. If you cannot tell which repository is meant, stop and ask. Report the bound repository and index freshness alongside your explanation. list repos is paginated, so page with offset: pagination.nextOffset until hasMore is false before concluding a repository is absent. Workflow If step 2 says "Index is stale" → run node .gitnexus/run.cjs analyze in terminal. Checklist Resources Resource What you get gitnexus://repo/{name}/context Stats, staleness warning (~150 tokens) gitnexus://repo/{name}/clusters All functional areas with cohesion scores (~300 tokens) gitnexus://repo/{name}/cluster/{name} Area members with file paths (~500 tokens) gitnexus://repo/{name}/process/{name} Step by step execution trace (~200 tokens) Tools query — find execution flows related to a concept: context — 360 degree view of a symbol: repo is required once more than one repository is indexed, and may be omitted with a single one. Example: "How does payment processing work?" Had step 1 returned two repositories, every call above would carry repo: "my app" .

gitnexus-exploring