gitnexus-debugging

Trace the root cause of code errors by querying execution flows with gitnexus_query, inspecting callers and callees via gitnexus_context, and reading process URIs. This workflow diagnoses failures across backend services, libraries, and integrations to pinpoint exact error sources.

Visualize a call graph for debugging by retrieving caller and callee relationships using gitnexus_context, or by running custom path queries with gitnexus_cypher. This maps execution paths and process interactions to clarify how failures propagate through the codebase.

Yes, you can perform deterministic tracing for API integrations without external dependencies. The Skill uses internal gitnexus_query, gitnexus_context, and gitnexus_cypher tooling to provide accessible context and traceable call graphs for diagnosing integration failures.

Start debugging a vague error symptom by passing the symptom description directly into gitnexus_query to find related execution flows. This identifies matching processes and provides accessible context to begin tracing the failure's execution path.

Use custom Cypher queries for code analysis when standard tracing does not expose the required execution path. Running gitnexus_cypher with custom MATCH path queries allows you to define specific traces to diagnose complex or deeply nested root causes.