skills.rest
ibytechaos
ibytechaosCOMMUNITY
Explore all skills by this author →
GitHub

gitnexus-debugging

Traces bugs and errors through codebases using GitNexus call graphs and execution flows.

1|Updated Oct 11, 2025
Search Tags:#debugging#root cause analysis#mcp#call graph#error tracing#cypher#gitnexus
One-click install
npx skills add https://github.com/ibytechaos/claude --skill gitnexus-debugging-ibytechaos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-debugging
Source: https://github.com/ibytechaos/claude/tree/main/plugins/gitnexus/skills/gitnexus-debugging
Command: npx skills add https://github.com/ibytechaos/claude --skill gitnexus-debugging-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gitnexus.

What problem does it solve? Debugging unfamiliar or large codebases is slow because finding where an error originates and who calls the failing function requires manual searching. This Skill uses the GitNexus code knowledge graph to trace errors, callers, and execution flows directly. ## Core Features & Use Cases - Error Tracing: Query the code graph for error text or symptoms to find related processes and suspect functions. - Call Graph Inspection: View incoming and outgoing calls for any function to understand data flow and external dependencies. - Custom Cypher Traces: Run Cypher queries for multi-hop call chain analysis when standard tools are insufficient. - Use Case: When an endpoint returns 500 intermittently, query for the error, inspect the suspect function's context to find an external API call, and trace the execution flow to identify a missing timeout as the root cause. ## Quick Start Ask the assistant to trace why a specific function or endpoint is failing using GitNexus.

Frequently Asked Questions about gitnexus-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace where an error comes from in a codebase?▼

Use gitnexus_query with the error text or symptom to find related processes and symbols, then run gitnexus_context on the suspect function to see its callers and callees. Reading the process resource traces the full execution flow to the root cause.

How do I find who calls a specific function?▼

Run gitnexus_context with the function name to list incoming calls (callers) and outgoing calls (callees). For multi-hop call chains, use gitnexus_cypher with a Cypher query matching CodeRelation CALLS edges.

What is GitNexus and how does it help debugging?▼

GitNexus is a code knowledge graph exposed through an MCP server that indexes symbols, call relations, and execution processes in a repository. It lets you query code semantically and trace call chains instead of manually grepping files.

Why does GitNexus say the index is stale?▼

The stale index message means the repository graph is out of date relative to recent code changes. Run npx gitnexus analyze in the terminal to rebuild the index before querying again.

Can GitNexus help with intermittent or performance bugs?▼

Yes. For intermittent failures, inspect a function's context for external calls and async dependencies. For performance issues, look for symbols with many callers to identify hot paths, and use detect_changes to assess recent regressions.

Related Skills

Explore More Software Engineering Skills→
MarbleSodasMarbleSodas

gitnexus-explorer

Index a git repository into a queryable knowledge graph with an interactive web UI.

Community
Intermediate
lekemulalekemula

rails-test-fixer

Diagnose and fix failing Rails tests by executing tests and analyzing failure outputs.

Community
Intermediate
tktaftktaf

recent-code-bugfix

Identify and fix bugs from the author's recent Git commits.

Community
Intermediate
CaptainPhantasyCaptainPhantasy

debug-breakpoint-inject

Inject log-based breakpoints to trace runtime variables during execution.

Community
Advanced