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"
SkillScore55Maintained
Automatic
◆Coding pack
Last verified 8/27/2026
What it changes
Passed 8 of 14 test cases with the skill, and 3 of 14 without it.
Without skill18%
With skill55%
Checks it passed that the model alone missed
The response uses gitnexus_cypher to query graph paths.
The response calls gitnexus_query with the error string.
The response query matches CodeRelation relationships with type CALLS.
and 8 more in the full report
9 fixed3 passed either way9 still failing1 broke
Pass-rate lift
+36 pp
Tokens
-22%
Agent turns
0%
Response time
-32%
Model gemini-3.6-flashMeasured 8/27/2026v112 of 22 cases passed with skill · 14 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
What is the exact URI path syntax to inspect the process map for a process named `OrderFulfillment` in repository `ecom-api`?
What was checked, without and with the skill
Checked
Without skill
With skill
The response specifies the URI schema format gitnexus://repo/ecom-api/process/OrderFulfillment.
Missed
Passed
case-15 · gemini-3.6-flash · 8/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md84 linessingle file
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 analyze in 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