skills.rest
cryborg1211
cryborg1211COMMUNITY
Explore all skills by this author →
GitHub

Debug Issue

Diagnose code issues by traversing knowledge graph relationships between functions and execution paths.

Updated May 10, 2026
Search Tags:#debugging#traceability#code-analysis#root-cause#knowledge-graph#flow-analysis
One-click install
npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill debug-issue-cryborg1211
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Debug Issue
Source: https://github.com/cryborg1211/quant_trading_telegram_bot/tree/main/.vibecode-backup/.claude/skills/debug-issue
Command: npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill debug-issue-cryborg1211

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace and fix code issues efficiently using a knowledge graph to map relationships between functions, files, and execution paths.

Core Features & Use Cases

  • Semantic graph navigation to locate issue sources by tracing callers_of and callees_of relationships.
  • Visualize full execution paths with get_flow to understand propagation and identify root causes.
  • Analyze recent changes and their impact with detect_changes and get_impact_radius to assess ripple effects.

Quick Start

Trace the root cause of a failing issue by querying the knowledge graph for the relevant callers and callees and then inspect the execution flow.

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 a complex codebase?▼

To trace the root cause of a code issue, you can navigate a knowledge graph of functions and files using callers_of and callees_of relationships to locate the exact source of the failure.

What is the best way to analyze code changes and assess their impact radius?▼

Analyzing code changes and their impact radius involves detecting recent modifications and querying the knowledge graph to visualize ripple effects across execution paths and related functions.

How does graph traversal work for debugging execution paths and function propagation?▼

Graph traversal for debugging execution paths works by mapping relationships between functions and files, enabling you to visualize full execution flows and identify exactly where propagation occurs.

Can I use this approach to debug CI failures and refactoring issues?▼

Yes, you can use knowledge graph navigation to debug CI failures and refactoring issues by traversing function relationships and execution paths to pinpoint the root cause of the regression.

How do I get minimal context when diagnosing code issues without loading the entire codebase?▼

To get minimal context when diagnosing code issues, you can query the knowledge graph to retrieve only the necessary function relationships and execution flow details, avoiding full codebase loads.

Related Skills

Explore More Software Engineering Skills→
jeremylongshorejeremylongshore
2

knowledge_graph

Build and query knowledge graphs from code or documents with natural-language queries.

Community
Intermediate
fmflurryfmflurry
171

eslint-true-server-error-resolution

Diagnose and resolve recurring ESLint server errors with targeted tests.

Community
Intermediate
tiroqtiroq

graphify

Transform code, documents, and images into a persistent knowledge graph.

Community
Advanced
htlin222htlin222
77

error-detective

Search and analyze log files and codebases for error patterns and stack traces.

Community
Intermediate