skills.rest
BenSheridanEdwards
BenSheridanEdwardsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gitnexus-debugging

Trace bugs and errors through code call graphs using GitNexus queries.

3|5|Updated Apr 26, 2026
Search Tags:#debugging#root cause analysis#code navigation#call graph#error tracing#cypher#gitnexus
One-click install
npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill gitnexus-debugging-bensheridanedwards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-debugging
Source: https://github.com/BenSheridanEdwards/ArchitectPlaybook/tree/main/.claude/skills/gitnexus/gitnexus-debugging
Command: npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill gitnexus-debugging-bensheridanedwards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging unfamiliar code often means manually grepping for error text and guessing at call chains. This Skill uses the GitNexus code graph to trace errors to their root cause by following actual caller/callee relationships and execution flows. ## Core Features & Use Cases - Error Tracing: Search for error text or symptoms, then inspect suspect functions to see their incoming and outgoing calls. - Call Chain Analysis: Find the shortest call path between two symbols with the trace tool, or write custom Cypher queries for complex traces. - Execution Flow Inspection: Read process resources to see step-by-step flows like a checkout pipeline and pinpoint where failures occur. - Use Case: When an endpoint returns a 500 intermittently, query for the error, inspect the suspect function's outgoing calls, and discover it calls an external API without a timeout. ## Quick Start Ask the assistant to trace why a specific function or endpoint is failing using the GitNexus debugging workflow.

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

Search for the error text with the query tool to find related symbols and processes, then run context on the suspect function to see its callers and callees. Read the process resource to follow the execution flow to the root cause.

How to find the call chain between two functions?▼

Use the trace tool with a from and to symbol name to get the shortest call chain in one call. If no path exists, it reports the furthest reachable node, showing where the chain breaks due to dynamic dispatch or external boundaries.

What does the GitNexus index stale warning mean?▼

A stale index warning means the code graph is out of date with recent changes. Run node .gitnexus/run.cjs analyze in the terminal to re-index the repository before continuing debugging.

When should I use Cypher queries instead of context for debugging?▼

Use Cypher when you need custom call chain traces that context cannot express, such as matching multi-hop CALLS relationships with variable path lengths. For standard caller/callee inspection, context is sufficient.

Can this approach find the cause of intermittent failures?▼

Yes. Inspect the suspect function with context and look for external calls or asynchronous dependencies among its outgoing edges. Intermittent failures often originate from external API calls lacking timeouts or error handling.

Related Skills

Explore More Software Engineering Skills→
shysssthanhtrishysssthanhtri

gitnexus-exploring

Trace execution flows and call relationships in indexed GitNexus repositories.

Community
Intermediate
denis-pingindenis-pingin

fixme-research

Identify root causes and generate fix strategies from codebase analysis.

Community
Intermediate
xtrm-devxtrm-dev
4

gitnexus-debugging

Trace execution paths and callers to identify root causes of code failures.

Official
Intermediate
hamzaPixlhamzaPixl
2

intel

Search code, artifacts, and event logs with ranked relevance via FTS5/BM25.

Community
Intermediate