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.