skills.rest
VoTruongDanh
VoTruongDanhCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Identify the root cause of software bugs through stepwise evidence analysis.

2|Updated Mar 5, 2026
Search Tags:#debugging#memory#evidence#root-cause-analysis#bug-fix#system-diagnostics
One-click install
npx skills add https://github.com/VoTruongDanh/Skills-Agent --skill debug-votruongdanh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/VoTruongDanh/Skills-Agent/tree/main/.cursor/skills/debug
Command: npx skills add https://github.com/VoTruongDanh/Skills-Agent --skill debug-votruongdanh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify the real root cause of bugs, failed commands, and unexpected software behavior, reducing debugging time and guesswork.

Core Features & Use Cases

  • Systematic root-cause analysis guided by memory context, logs, and structured hypotheses.
  • Socratic gate to verify assumptions, gather evidence, and rank hypotheses.
  • Cross-domain routing to leverage specialized agents for API/server, UI, database, or security issues.
  • Clear, actionable fixes with updated memory and post-mortem lessons.

Quick Start

Start root-cause analysis by describing the failing scenario to the debugger.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I find the root cause of a software bug instead of just guessing?▼

Root-cause analysis identifies the real cause of bugs by enforcing memory context, stepwise analysis, and evidence gathering. It guides you through structured hypotheses ranking to eliminate guesswork and quickly resolve software failures.

What is the best way to debug API server failures and database issues systematically?▼

Systematic debugging for API, server, database, and UI issues uses cross-domain routing to leverage specialized analysis. It applies a Socratic gate to verify assumptions and gather evidence before proposing a documented fix.

How do I start a root-cause analysis when a command fails unexpectedly?▼

Start root-cause analysis by describing the failing scenario to the debugger. The process applies memory context and structured hypotheses to systematically investigate the unexpected software behavior and identify the failure point.

Does this debugging approach work for both UI and security-related issues?▼

Yes, root-cause analysis applies to API, server, UI, database, and security-related issues. It routes the specific failure domain to specialized agents to verify assumptions and gather relevant evidence for the fix.

Why should I use structured hypotheses ranking for bug fixes?▼

Structured hypotheses ranking prioritizes potential root causes based on gathered evidence and memory context. This systematic approach reduces debugging time by verifying assumptions through a Socratic gate before applying a fix.

Related Skills

Explore More Software Engineering Skills→
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
LinnkidChenLinnkidChen
4

break-loop

Document root causes and preventive measures after debugging sessions.

Community
Advanced
Moliboy5000Moliboy5000

trace

Generate, evaluate, and rank competing hypotheses to explain observed results.

Community
Advanced
thisisqubikathisisqubika

security-review

Analyze code repositories for vulnerabilities using SAST and AI triage.

Official
Advanced