debug

Guides systematic root-cause analysis before applying fixes in multi-component systems.

Updated Jan 6, 2026

Search Tags:#debugging #evidence #reproduce #phases #root-cause #bugfix #stack-trace

Ready to run

npx skills add https://github.com/devseunggwan/praxis --skill debug-devseunggwan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/devseunggwan/praxis/tree/main/skills/debug
Command: npx skills add https://github.com/devseunggwan/praxis --skill debug-devseunggwan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging reduces guesswork by focusing on root causes before proposing fixes.

Core Features & Use Cases

Phase-guided investigation covering error reading, reproduction, evidence gathering, and data tracing.
Delegates analysis to agent roles (debugger, test-engineer, ultraqa) for rapid root-cause isolation.
Applicable to test failures, production bugs, performance issues, and integration problems.

Quick Start

Reproduce the issue reliably, collect trace data, and identify the failing component before attempting any fix.

Frequently Asked Questions about debug

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

FAQPage Schema

What is root-cause debugging and how does it speed up bug fixes?▼

Root-cause debugging identifies the fundamental reason for software issues before applying fixes. It uses a structured, phase-based workflow to reduce guesswork and ensure the actual problem is resolved.

How do I systematically debug flaky tests and performance slowdowns?▼

Systematic debugging of flaky tests and performance slowdowns follows phase-guided steps: reliably reproduce the issue, gather trace data, and isolate the failing component before attempting any fix.

Can I use a phase-based workflow to debug multi-component integration failures?▼

Yes, phase-based debugging applies to multi-component integration failures. It delegates analysis to specialized agent roles for rapid root-cause isolation across software issues, build failures, and test failures.

What's the best way to collect evidence and read stack traces during bug investigation?▼

The best way to collect evidence and read stack traces is using a structured investigation workflow covering error reading, reproduction, evidence gathering, and data tracing to pinpoint the root cause.

When should I use a structured debugging workflow instead of guessing fixes?▼

Use structured debugging when facing complex production bugs, flaky tests, or performance issues where guessing fixes is inefficient. It ensures you analyze patterns and gather evidence before implementation.