skills.rest
sarthkdobriyal
sarthkdobriyalCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug-issue

Trace and debug code issues using knowledge graph navigation tools.

Updated Aug 4, 2026
Search Tags:#debugging#knowledge graph#root cause analysis#semantic search#impact analysis#code navigation#call tracing
One-click install
npx skills add https://github.com/sarthkdobriyal/hisaabi --skill debug-issue-sarthkdobriyal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-issue
Source: https://github.com/sarthkdobriyal/hisaabi/tree/main/.gemini/skills/debug-issue
Command: npx skills add https://github.com/sarthkdobriyal/hisaabi --skill debug-issue-sarthkdobriyal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging unfamiliar or large codebases often means hours of manual searching through files to understand call chains and locate the source of a bug. This Skill provides a systematic workflow that uses a code knowledge graph to trace issues from symptom to root cause. ## Core Features & Use Cases - Semantic Code Search: Find code related to an issue using semantic_search_nodes_tool instead of guessing file locations. - Call Chain Tracing: Use query_graph_tool with callers_of and callees_of plus get_flow to follow full execution paths through suspected areas. - Change & Impact Analysis: Run detect_changes_tool to check whether recent changes caused the issue, and get_impact_radius_tool to see what else a suspected file affects. - Use Case: A bug report says checkout fails after a recent commit. Start with get_minimal_context, trace the callers of the failing function, check recent changes, and confirm the blast radius before proposing a fix. ## Quick Start Debug the reported issue by starting with get_minimal_context, then trace callers and callees of the suspected code and check recent changes for the root cause.

Frequently Asked Questions about debug-issue

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

FAQPage Schema
How do I debug an issue using a code knowledge graph?▼

Start with get_minimal_context to load a minimal view of the relevant code, then use semantic search to find related nodes. Trace callers and callees of suspected functions, inspect execution flows, and check recent changes to identify the root cause.

How to trace function call chains in a large codebase?▼

Use query_graph_tool with callers_of and callees_of to walk up and down the call chain from a suspected function. Then run get_flow to see the full execution path through the affected area and find the entry point triggering the bug.

Can graph-based debugging find regressions from recent changes?▼

Yes. Run detect_changes_tool to list recent modifications and correlate them with the failing behavior. Recent changes are the most common source of new issues, so checking them early narrows the search quickly.

How do I check what else a buggy file affects?▼

Use get_impact_radius_tool on the suspected file to see all code that depends on it. This reveals the blast radius of a potential fix and helps avoid introducing regressions elsewhere.

Why does graph debugging use minimal detail level by default?▼

The minimal detail level keeps tool output small so debugging stays within roughly five tool calls and 800 output tokens. Escalate to standard detail only when the minimal view is insufficient to resolve the issue.

Related Skills

Explore More Software Engineering Skills→
MinhHoangDonoMinhHoangDono

ck:gkg

Builds a symbol graph from AST parsing to query definitions, usages, and relationships in Git repositories.

Community
Intermediate
emdash-cmsemdash-cms
12.1k

fix

Implements diagnosed bug fixes, runs focused verification, and publishes candidate branches.

Official
Advanced
nam3886nam3886

ck:watzup

Review recent git commits and summarize file changes and impact.

Community
Intermediate
chkp-ronizchkp-roniz
4

debugger

Diagnose Python bugs via MCPDebug breakpoints and runtime state inspection in VS Code.

Community
Advanced