skills.rest
gmolike
gmolikeCOMMUNITY
Explore all skills by this author →
GitHub

gitnexus-debugging

Trace bugs and errors through codebases using GitNexus graph queries and execution flows.

Updated Mar 4, 2026
Search Tags:#debugging#root cause analysis#call graph#error tracing#cypher#code graph#gitnexus
One-click install
npx skills add https://github.com/gmolike/Claude-Template --skill gitnexus-debugging-gmolike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-debugging
Source: https://github.com/gmolike/Claude-Template/tree/main/.claude/skills/gitnexus-debugging
Command: npx skills add https://github.com/gmolike/Claude-Template --skill gitnexus-debugging-gmolike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging unfamiliar or large codebases often means guessing where an error originates and manually tracing call chains. This Skill uses the GitNexus code graph to locate error sources, trace callers and callees, and follow execution flows to a root cause. ## Core Features & Use Cases - Index Freshness Verification: Compares the indexed commit against HEAD before querying, preventing traces based on stale code that no longer exists. - Symptom-to-Suspect Tracing: Uses gitnexus_query to find code related to an error message, then gitnexus_context to inspect callers, callees, and process steps. - Custom Call Chain Queries: Supports Cypher queries for multi-hop call chain traces when standard tools are insufficient. - Use Case: When a payment endpoint returns 500 intermittently, query for the error handling flow, inspect the suspect function's outgoing calls, and discover an external API call missing a timeout. ## Quick Start Ask the AI to debug why a specific endpoint or function is failing and trace the error to its root cause using the GitNexus code graph.

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?▼

Query the GitNexus graph with the error text using gitnexus_query to find related processes and symbols, then run gitnexus_context on the suspect function to see its callers and callees. Read the process resource to follow the execution flow step by step.

How do I find who calls a specific function?▼

Use gitnexus_context with the function name to list incoming calls (callers) and outgoing calls (callees). For deeper multi-hop chains, write a Cypher query matching CodeRelation CALLS edges up to the desired depth.

Why does GitNexus return results for code that no longer exists?▼

The GitNexus index does not update automatically after commits or merges, so it can answer from stale code. Run npx gitnexus status and confirm the indexed commit equals git rev-parse HEAD; if not, run npx gitnexus analyze first.

Does npx gitnexus status fail when the index is stale?▼

No, npx gitnexus status exits with code 0 in every case, including a stale index or an unindexed repository. You must parse its stdout and compare the indexed commit to HEAD rather than branching on the exit code.

What debugging symptoms can GitNexus help investigate?▼

It covers error messages, wrong return values, intermittent failures, performance issues, and recent regressions. Each symptom maps to an approach such as querying error text, tracing callees for data flow, or using detect_changes to see what your changes affect.

Related Skills

Explore More Software Engineering Skills→
ibytechaosibytechaos
1

gitnexus-impact-analysis

Analyzes code change blast radius and dependency impact using GitNexus symbol graphs.

Community
Intermediate
dmae97dmae97
130

omk-flow-bugfix

Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.

Community
Intermediate
KumarAdi8KumarAdi8

debugging-instruments

Diagnose iOS crashes, memory leaks, and hangs using LLDB and Instruments.

Community
Advanced
AcendasAcendas
3

ad-trace

Trace Android code paths by instrumenting logpoints across a suspect call graph.

Official
Advanced