// 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"
| name | gitnexus-exploring |
| description | 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" |
1. READ gitnexus://repos ā Discover indexed repos
2. READ gitnexus://repo/{name}/context ā Codebase overview, check staleness
3. gitnexus_query({query: "<what you want to understand>"}) ā Find related execution flows
4. gitnexus_context({name: "<symbol>"}) ā Deep dive on specific symbol
5. READ gitnexus://repo/{name}/process/{name} ā Trace full execution flow
If step 2 says "Index is stale" ā run
npx gitnexus analyzein terminal.
- [ ] READ gitnexus://repo/{name}/context
- [ ] gitnexus_query for the concept you want to understand
- [ ] Review returned processes (execution flows)
- [ ] gitnexus_context on key symbols for callers/callees
- [ ] READ process resource for full execution traces
- [ ] Read source files for implementation details
| 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) |
gitnexus_query ā find execution flows related to a concept:
gitnexus_query({query: "payment processing"})
ā Processes: CheckoutFlow, RefundFlow, WebhookHandler
ā Symbols grouped by flow with file locations
gitnexus_context ā 360-degree view of a symbol:
gitnexus_context({name: "validateUser"})
ā Incoming calls: loginHandler, apiMiddleware
ā Outgoing calls: checkToken, getUserById
ā Processes: LoginFlow (step 2/5), TokenRefresh (step 1/3)
1. READ gitnexus://repo/my-app/context ā 918 symbols, 45 processes
2. gitnexus_query({query: "payment processing"})
ā CheckoutFlow: processPayment ā validateCard ā chargeStripe
ā RefundFlow: initiateRefund ā calculateRefund ā processRefund
3. gitnexus_context({name: "processPayment"})
ā Incoming: checkoutHandler, webhookHandler
ā Outgoing: validateCard, chargeStripe, saveTransaction
4. Read src/payments/processor.ts for implementation details
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?"
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
Use when the user asks about GitNexus itself ā available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"