gitnexus-debugging

To trace an error message to its root cause, query the reported bug using gitnexus_query to search across the codebase. Then inspect call relationships with gitnexus_context to expose callers and callees, illuminating the execution path where the error originates.

Call graph analysis for software debugging works by mapping function relationships and execution paths. It exposes who calls whom within processes, allowing you to follow the exact execution flow and identify where an error originates in the code.

To inspect callers and callees when diagnosing a bug, use gitnexus_context to see call relationships. You can then read the specific process via gitnexus://repo/{name}/process/{name} to follow the execution path and confirm the root cause.

Yes, you can generate custom traces for complex call graphs by using gitnexus_cypher. This allows you to craft tailored traces that confirm the root cause of a bug when standard execution flow tracing is insufficient.

You need to describe the bug briefly and ask to trace its origin. The Skill uses gitnexus_query to search for error messages or symptoms across the codebase, mapping the reported issue to its origin in the code paths.

The best way to locate the source of a bug in a complex process is to trace the execution flow via gitnexus://repo/{name}/process/{name}. If needed, generate targeted traces with gitnexus_cypher to confirm the root cause.