skills.rest
changfengpro
changfengproCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gitnexus-debugging

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging unfamiliar code often means manually searching for error messages and guessing which functions are involved. This Skill uses the GitNexus code knowledge graph to trace errors to their root cause by following call chains and execution flows. ## Core Features & Use Cases - Error Tracing: Query for error text to find related processes and symbols, then inspect callers and callees of suspect functions. - Execution Flow Analysis: Read process resources to follow step-by-step execution flows and pinpoint where failures occur. - Custom Call Chain Queries: Use Cypher queries to trace multi-hop call relationships for complex investigations. - Use Case: When a payment endpoint returns 500 intermittently, query for the error, inspect the suspect function's outgoing calls, and discover an external API call missing a timeout. ## Quick Start Ask the AI to trace why a specific function or endpoint is failing using GitNexus, starting from the error message you observed.

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

Start with gitnexus_query using the error text 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 to find who calls a function in a codebase?▼

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

What does the GitNexus index is stale message mean?▼

A stale index means the knowledge graph no longer reflects the current code. Run npx gitnexus analyze in the terminal to rebuild the index before continuing your debugging session.

Can GitNexus help debug intermittent failures?▼

Yes. Run gitnexus_context on the failing function and look for external calls or asynchronous dependencies in its outgoing calls, which are common sources of intermittent behavior such as missing timeouts on external APIs.

When should I use Cypher queries instead of gitnexus_context?▼

Use gitnexus_cypher when you need custom call chain traces beyond direct callers and callees, such as paths of depth two or more. For standard single-function inspection, gitnexus_context is sufficient.

Related Skills

Explore More Software Engineering Skills→
ruskicoderruskicoder
3

codebase-understanding

Analyze codebase structure, call flows, and change impact using the GitNexus knowledge graph.

Community
Intermediate
PyModelPyModel
18

gitnexus-debugging

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

Official
Intermediate
AniTrendAniTrend
51

code-review-graph-debug

Trace bug root cause and impact using a code-review knowledge graph.

Official
Advanced
CaptainPhantasyCaptainPhantasy

debug-breakpoint-inject

Inject log-based breakpoints to trace runtime variables during execution.

Community
Advanced