Gitnexus Debugging

This prompt helps Claude trace bugs by querying your GitNexus code graph instead of grepping files. When you hit an error or unexpected behavior, it walks through finding related execution flows, inspecting callers and callees, and tracing the actual call chain that leads to the problem. The workflow is structured around four steps: query for the symptom, get context on suspects, read execution flows, and run custom graph queries if needed. What's useful here is the debugging patterns table that maps common symptoms like intermittent failures or performance issues to specific GitNexus approaches. It's built for the moment when you're staring at a 500 error and need to understand what actually calls what.

skills.sh installs: 1.8K
GitHub stars: 48.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add abhigyanpatwari/gitnexus --skill gitnexus-debugging --agent claude-code

Installs into .claude/skills of the current project.

Files

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

Bind the repository first

A root cause traced in the wrong repository is a wrong root cause.

Bind once using a confirmed registry name/path or configured MCP default. Call list_repos {} if the target is not yet known; reuse that binding across calls. With one indexed repository, use the examples below as written. With more than one, pass repo on every call: an omitted repo normally errors, but under an MCP policy with a configured default it resolves to that default silently. If you cannot tell which repository is meant, stop and ask. This matters most for cypher, whose statement carries no in-band hint of which database it ran against.

list_repos is paginated, so page with offset: pagination.nextOffset until hasMore is false before concluding a repository is absent.

A stale index describes the code from before your bug, so refresh before trusting a trace, and state the repository and index freshness with the diagnosis.