gitnexus-debugging

Trace error symptoms to execution paths and call graphs using GitNexus queries.

1|Updated Apr 9, 2026

Search Tags:#debugging #traceability #error-analysis #call-graph #software-debugging #code-tracing #gitnexus

Ready to run

npx skills add https://github.com/hbvg234/jnmt.vn --skill gitnexus-debugging-hbvg234

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitnexus-debugging
Source: https://github.com/hbvg234/jnmt.vn/tree/main/Claude-code/.claude/skills/gitnexus/gitnexus-debugging
Command: npx skills add https://github.com/hbvg234/jnmt.vn --skill gitnexus-debugging-hbvg234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers to debug code more efficiently by tracing errors through GitNexus, revealing execution flows and caller/callee relationships.

Core Features & Use Cases

GitNexus query to locate error text or related code
gitnexus_context to inspect suspect function context
READ gitnexus://repo/{name}/process/ to trace execution flow
gitnexus_cypher for custom traces
If the index is stale, run npx gitnexus analyze in terminal

Quick Start

Start by running gitnexus_query for the error text to locate related flows

Frequently Asked Questions about gitnexus-debugging

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

FAQPage Schema

How do I trace an error to its origin across different modules?▼

To trace an error to its origin across modules, map error symptoms to execution paths and call graphs. This approach locates where errors originate and reveals caller/callee relationships to pinpoint root causes.

What is the best way to debug code using call graphs and execution paths?▼

Debugging code with call graphs involves mapping error symptoms to execution paths. By querying error text, inspecting suspect function context, and tracing process flows, you can locate root causes efficiently.

How do I track data flow and find who calls a function during a debugging session?▼

To track data flow and find who calls a function during debugging, map execution paths and call graphs. This traces how data moves through services and identifies all callers of the target function.

Can I run custom traces for error analysis if the index is stale?▼

Yes, you can run custom traces for error analysis using cypher-based queries. If the index is stale, run the npx gitnexus analyze command in the terminal to refresh it before tracing execution flows.

Does step-wise debugging work for locating errors across multiple services?▼

Step-wise debugging works for locating errors across multiple services by applying context extraction and process tracing. It maps caller/callee relationships to reveal how data flows between different modules.

Why does my error tracing not return the expected execution flow?▼

Error tracing might not return the expected execution flow if the repository index is stale. Run npx gitnexus analyze in your terminal to rebuild the index, then retry querying the error text and process paths.