gitnexus-debugging — Claude Code skill: debugging and setup
This skill traces bugs through repository symbols, callers, processes, and call chains. Use it when an error needs a concrete source.
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-debugging -a claude-codeWhat gitnexus-debugging does
gitnexus-debugging investigates bugs and unexpected behavior with GitNexus. It binds the investigation to a repository, searches for the error or related code, inspects the suspected symbol, and follows calls when the execution path needs more evidence.
The workflow uses list_repos, query, context, trace, and cypher. A process resource is read only when its trace answers an open question. With multiple indexed repositories, every call needs repo; an ambiguous target should stop the investigation. Check index freshness before trusting a diagnosis, and run node .gitnexus/run.cjs analyze when the status is behind or diverged.
The skill keeps partial and unknown relations visible and asks for source and test confirmation before claiming a root cause. A stale index or wrong repository can point to the wrong explanation, so verify both alongside the diagnosis.
What it helps with
- locate where an error message is raised
- trace a call path between two symbols
- investigate failures around external API calls
- inspect the impact of a recent code change
Example prompts for the agent
- Investigate `payment validation error` in repository `my-app` and identify the function where it originates.
- Trace the shortest call chain from `processCheckout` to `fetchRates` in `my-app`.
- Find out why the payment endpoint intermittently returns 500 and report the repository and index freshness.
How to install gitnexus-debugging
1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-debugging -a claude-code2Manually: put the files in place
~/.claude/skills/gitnexus-debugging/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gitnexus-debugging/
1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-debugging -a codex2Manually: put the files in place
.agents/skills/gitnexus-debugging/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-debugging -a cursor2Manually: put the files in place
.cursor/skills/gitnexus-debugging/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install abhigyanpatwari/GitNexus gitnexus-debugging2Manually: put the files in place
.github/skills/gitnexus-debugging/SKILL.md1Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-debugging -a gemini-cli2Platform CLI
gemini skills install https://github.com/abhigyanpatwari/GitNexus --path gitnexus-claude-plugin/skills/gitnexus-debuggingManually: put the files in place
.devin/skills/gitnexus-debugging/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add abhigyanpatwari/GitNexus --skill gitnexus-debugging -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set6
The whole set →Similar
Questions about gitnexus-debugging
How do I install gitnexus-debugging in Claude Code?
Run npx skills add abhigyanpatwari/GitNexus --skill gitnexus-debugging -a claude-code, run npx skills add abhigyanpatwari/GitNexus --skill gitnexus-debugging -a claude-code again, then open ~/.claude/skills/gitnexus-debugging/SKILL.md.
What does gitnexus-debugging do?
It investigates bugs by finding related code, showing incoming and outgoing calls, tracing paths between symbols, and checking the effect of changes.
What should I do when the GitNexus index is stale?
Run node .gitnexus/run.cjs analyze for behind or diverged statuses. Include the repository and index freshness in the diagnosis.