// 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 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"
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, graph schema, or workflow reference.
Trace bugs through call chains using knowledge graph
| 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 ....
Multi-repo note: Always pass
--repo <name>to every command to avoid "multiple repositories" errors.
1. gitnexus list → Discover indexed repos
2. gitnexus status → Check index freshness
3. gitnexus query "<what you want to understand>" --repo <name> → Find related execution flows
4. gitnexus context "<symbol>" --repo <name> → Deep dive on specific symbol
5. Read source files from the returned file paths for implementation details
If step 2 says the index is stale → run
gitnexus analyzein terminal.
- [ ] gitnexus status to verify index freshness
- [ ] gitnexus query for the concept you want to understand
- [ ] Review returned processes (execution flows) and file paths
- [ ] gitnexus context on key symbols for callers/callees
- [ ] Read source files for implementation details
gitnexus query — find execution flows related to a concept:
gitnexus query "payment processing" --repo my-app
# → Processes: CheckoutFlow, RefundFlow, WebhookHandler
# → Symbols grouped by flow with file locations
gitnexus context — 360-degree view of a symbol:
gitnexus context "validateUser" --repo my-app
# → Incoming calls: loginHandler, apiMiddleware
# → Outgoing calls: checkToken, getUserById
# → Processes: LoginFlow (step 2/5), TokenRefresh (step 1/3)
gitnexus cypher — custom graph queries for structural exploration:
gitnexus cypher 'MATCH (f:Function)-[:MEMBER_OF]->(c:Class {name: "PaymentService"}) RETURN f.name, f.filePath' --repo my-app
# 1. Check index is fresh
gitnexus status
# 2. Find execution flows for the concept
gitnexus query "payment processing" --repo my-app
# → CheckoutFlow: processPayment → validateCard → chargeStripe
# → RefundFlow: initiateRefund → calculateRefund → processRefund
# 3. Deep dive on the main entry point
gitnexus context "processPayment" --repo my-app
# → Incoming: checkoutHandler, webhookHandler
# → Outgoing: validateCard, chargeStripe, saveTransaction
# 4. Read src/payments/processor.ts for implementation details