gitnexus-debugging
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\"
Best for Root cause analysisWorks with GitHubLow risk
⌘source
- author
@abhigyanpatwari- language
- TypeScript
★28kstars
3.2kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Finds related execution flows for errors
- ·Shows callers and callees of suspect functions
- ·Traces execution flow through process resources
- ·Allows custom call chain traces with Cypher queries
- ·Provides a structured debugging checklist
Use Cases
- →Investigating why a function is failing
- →Tracing the origin of an error message
- →Understanding who calls a specific method
- →Debugging an endpoint returning a 500 error
- →Analyzing unexpected behavior or bugs
Best for
- ✓Root cause analysis
- ✓Complex codebase debugging
FAQs
name
gitnexus-debugging
description
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"
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 |
$install
1-click copynpx skills add abhigyanpatwari/GitNexus --skill gitnexus-debuggingSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.