skills.rest
son-nguyen-301
son-nguyen-301COMMUNITY
Explore all skills by this author →
GitHub

debug

Guide structured debugging from symptoms to root-cause confirmation.

Updated Apr 6, 2026
Search Tags:#git#workflow#codebase#debug#root-cause#error-troubleshooting
One-click install
npx skills add https://github.com/son-nguyen-301/hydra-claude --skill debug-son-nguyen-301
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/son-nguyen-301/hydra-claude/tree/main/skills/debug
Command: npx skills add https://github.com/son-nguyen-301/hydra-claude --skill debug-son-nguyen-301

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Investigate and resolve bugs quickly by guiding a structured debugging workflow that takes you from symptoms to root cause.

Core Features & Use Cases

  • Stepwise debugging workflow: collect symptoms, narrow scope, perform deep investigation, confirm root cause, and produce a findings report.
  • Guided tool integration: leverage GitNexus queries when available to trace call graphs and recent changes, and reference methodology for best practices.
  • Proactive and reactive usage: invoke when users report bugs or plan tasks require bug-fixing analysis.

Quick Start

Provide the error message or stack trace to initiate structured debugging.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I troubleshoot an error using a structured root-cause analysis workflow?▼

To troubleshoot an error with root-cause analysis, the workflow guides you through collecting symptoms, narrowing scope, performing deep investigation, and confirming the root cause before producing a formal findings report.

What is the best way to debug a codebase when I only have an error message or stack trace?▼

The best way to debug a codebase from an error message is to input the stack trace to initiate a stepwise workflow, which systematically narrows the investigation scope and traces recent changes to isolate the fault.

Can I trace call graphs and recent git changes during the debugging process?▼

Yes, you can trace call graphs and recent git changes during the debugging process by leveraging optional GitNexus queries, which provide deep codebase traceability to help pinpoint the exact source of the bug.

Does this debugging workflow require any specific dependencies to run?▼

No specific dependencies are required to run this debugging workflow, though utilizing optional GitNexus queries and reference methodology can significantly enhance deep investigation and traceability.

What output or report format is generated after confirming a bug's root cause?▼

After confirming a bug's root cause, the workflow generates a formal debug report directly in the workspace, documenting the structured findings from the initial symptoms through to the final resolution.

Related Skills

Explore More Software Engineering Skills→
Space-DinosaursSpace-Dinosaurs
12

agent-debugger

Diagnose root causes of failing tests and stack traces from codebase inspection.

Official
Advanced
chriswesttchriswestt

gstack-openclaw-investigate

Identify bug root causes through symptom collection, code path tracing, and deterministic reproduction.

Community
Advanced
grafanagrafana
31

gitnexus-exploring

Trace execution flows and symbol relationships in unfamiliar codebases using GitNexus.

Official
Intermediate
belokonmbelokonm
8

error-detector

Detect software errors through static analysis, runtime monitoring, and log analysis.

Community
Advanced