Debug Issue

Trace and diagnose code issues by navigating call relationships in a knowledge graph.

Updated Aug 23, 2026

Search Tags:#debugging #troubleshooting #knowledge-graph #root-cause-analysis #call-graph #code-navigation

Ready to run

npx skills add https://github.com/WannaCry081/React-Workflow-Starter --skill debug-issue-wannacry081

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Debug Issue
Source: https://github.com/WannaCry081/React-Workflow-Starter/tree/main/.agents/skills/debug-issue
Command: npx skills add https://github.com/WannaCry081/React-Workflow-Starter --skill debug-issue-wannacry081

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace and diagnose code issues using a knowledge graph to understand call chains and execution paths.

Core Features & Use Cases

trace issues across callers and callees to find root causes
visualize execution paths with graph-based queries
perform impact analysis and plan fixes

Quick Start

Run the troubleshooting workflow to locate the entry point and follow the execution path using graph queries.

Frequently Asked Questions about Debug Issue

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

FAQPage Schema

How do I trace the root cause of a code issue across multiple files?▼

Root cause tracing across multi-file projects uses a knowledge graph to map execution paths and analyze caller and callee relationships. This approach visualizes call chains to pinpoint where failures originate.

What is a knowledge graph approach to debugging and troubleshooting?▼

Knowledge graph debugging models code relationships as nodes and edges, enabling targeted graph queries to trace execution paths. It replaces manual codebase searching with deterministic commands for context loading and safety.

How does call graph analysis work for finding execution paths?▼

Call graph analysis queries callers_of and callees_of relationships to reconstruct full execution paths. This deterministic tracing reveals the exact sequence of function invocations leading to an issue.

Can I perform impact analysis to plan fixes for multi-file projects?▼

Yes, you can perform impact analysis to plan fixes by traversing the call graph to identify all affected callers. This highlights the downstream blast radius of potential code changes before implementation.

Do I need predefined graph commands to navigate code relationships?▼

Yes, predefined graph commands are required to navigate code relationships deterministically. They ensure safety guards and minimal context loading while querying execution paths during troubleshooting.

What is the best way to diagnose code issues without exhaustive codebase searching?▼

The best way to diagnose code issues without exhaustive searching is using graph-based queries to locate entry points and follow execution paths. This targets specific call chains rather than scanning files.