gitnexus-debugging

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

18|8|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/PyModel/pythinker-code --skill gitnexus-debugging-pymodel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-debugging
Source: https://github.com/PyModel/pythinker-code/tree/main/.agents/skills/gitnexus/gitnexus-debugging
Command: npx skills add https://github.com/PyModel/pythinker-code --skill gitnexus-debugging-pymodel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging unfamiliar code often means manually grepping for error messages and guessing call chains. This Skill turns debugging into a structured investigation by querying a code knowledge graph to find where errors originate, who calls a suspect function, and how execution flows reach the failure point. ## Core Features & Use Cases - Error-to-Source Tracing: Search for error text or symptoms, then inspect callers and callees of suspect functions to locate the root cause. - Execution Flow Analysis: Read process resources and run Cypher queries to trace call chains, including a shortest-path trace between two symbols. - Regression Impact Checks: Use change detection to see what recent edits affect, helping diagnose regressions. - Use Case: A payment endpoint returns 500 intermittently. Query for the error handling flow, inspect the suspect validation function, discover it calls an external API without a timeout, and confirm the root cause in the source. ## Quick Start Ask the agent 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?

Query the GitNexus index for the error text or symptom, then run context on the suspect function to see its callers and callees. Read the process resource for the execution flow and confirm the root cause in the source files.

How to find the call chain between two functions?

Use the trace tool with a from and to symbol to get the shortest call chain in one call, including hop count and edge confidence. If no path exists, it reports the furthest reachable node where the chain breaks.

What should I do when the GitNexus index is stale?

Run node .gitnexus/run.cjs analyze in the terminal to rebuild the index. A stale index means query and context results may not reflect recent code changes.

Can I write custom queries to trace call relationships?

Yes, the cypher tool accepts Cypher statements against the code graph, such as matching CALLS relationships between functions. This supports custom call chain traces beyond the built-in query and context tools.

How do I check what my recent code changes affect?

Use the detect_changes tool to see which symbols and processes your edits impact. This is the recommended approach for investigating recent regressions after a change.