gitnexus-debugging
8
总安装量
6
周安装量
#35879
全站排名
安装命令
npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-debugging
Agent 安装分布
opencode
6
gemini-cli
6
github-copilot
6
codex
6
kimi-cli
6
amp
6
Skill 文档
Debugging with GitNexus
When to Use
- “Why is this function failing?”
- “Trace where this error comes from”
- “Who calls this method?”
- “This endpoint returns 500”
- Investigating bugs, errors, or unexpected behavior
Workflow
1. gitnexus_query({query: "<error or symptom>"}) â Find related execution flows
2. gitnexus_context({name: "<suspect>"}) â See callers/callees/processes
3. READ gitnexus://repo/{name}/process/{name} â Trace execution flow
4. gitnexus_cypher({query: "MATCH path..."}) â Custom traces if needed
If “Index is stale” â run
npx gitnexus analyzein terminal.
Checklist
- [ ] Understand the symptom (error message, unexpected behavior)
- [ ] gitnexus_query for error text or related code
- [ ] Identify the suspect function from returned processes
- [ ] gitnexus_context to see callers and callees
- [ ] Trace execution flow via process resource if applicable
- [ ] gitnexus_cypher for custom call chain traces if needed
- [ ] Read source files to confirm root cause
Debugging Patterns
| Symptom | GitNexus Approach |
|---|---|
| Error message | gitnexus_query for error text â context on throw sites |
| Wrong return value | context on the function â trace callees for data flow |
| Intermittent failure | context â look for external calls, async deps |
| Performance issue | context â find symbols with many callers (hot paths) |
| Recent regression | detect_changes to see what your changes affect |
Tools
gitnexus_query â find code related to error:
gitnexus_query({query: "payment validation error"})
â Processes: CheckoutFlow, ErrorHandling
â Symbols: validatePayment, handlePaymentError, PaymentException
gitnexus_context â full context for a suspect:
gitnexus_context({name: "validatePayment"})
â Incoming calls: processCheckout, webhookHandler
â Outgoing calls: verifyCard, fetchRates (external API!)
â Processes: CheckoutFlow (step 3/7)
gitnexus_cypher â custom call chain traces:
MATCH path = (a)-[:CodeRelation {type: 'CALLS'}*1..2]->(b:Function {name: "validatePayment"})
RETURN [n IN nodes(path) | n.name] AS chain
Example: “Payment endpoint returns 500 intermittently”
1. gitnexus_query({query: "payment error handling"})
â Processes: CheckoutFlow, ErrorHandling
â Symbols: validatePayment, handlePaymentError
2. gitnexus_context({name: "validatePayment"})
â Outgoing calls: verifyCard, fetchRates (external API!)
3. READ gitnexus://repo/my-app/process/CheckoutFlow
â Step 3: validatePayment â calls fetchRates (external)
4. Root cause: fetchRates calls external API without proper timeout