// 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"
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 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 CLI commands, how to query the knowledge graph, 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"
| 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" |
IMPORTANT — How to use GitNexus: GitNexus is a standalone CLI tool. Run it directly via
gitnexus <command>in the Bash tool. Do NOT usemcpl call gitnexus ...ornpx gitnexus ...— gitnexus is installed globally and invoked by name.
Multi-repo note: Always pass
--repo <name>to every command that operates on a specific repo to avoid "multiple repositories" errors.
1. gitnexus status → Check index freshness
2. gitnexus query "<what you want>" --repo <name> → Find related execution flows
3. gitnexus context "<symbol>" --repo <name> → Deep dive on specific symbol
4. Read source files from the output for implementation details
If step 1 says "Index is stale" → run
gitnexus analyzein terminal.
- [ ] gitnexus status — check index freshness
- [ ] gitnexus query for the concept you want to understand
- [ ] Review returned processes (execution flows)
- [ ] gitnexus context on key symbols for callers/callees
- [ ] Read source files for implementation details
All commands are run directly via the Bash tool. Do not use mcpl or npx.
| Command | What it gives you | Example |
|---|---|---|
gitnexus query "<concept>" --repo <name> | Process-grouped execution flows related to a concept | gitnexus query "payment processing" --repo <name> |
gitnexus context "<symbol>" --repo <name> | 360-degree symbol view — callers, callees, processes | gitnexus context "validateUser" --repo <name> |
gitnexus status | Index freshness check | gitnexus status |
1. gitnexus status → 918 symbols, 45 processes
2. gitnexus query "payment processing" --repo my-app
→ CheckoutFlow: processPayment → validateCard → chargeStripe
→ RefundFlow: initiateRefund → calculateRefund → processRefund
3. gitnexus context "processPayment" --repo my-app
→ Incoming: checkoutHandler, webhookHandler
→ Outgoing: validateCard, chargeStripe, saveTransaction
4. Read src/payments/processor.ts for implementation details