skills.rest
MinhThang1009
MinhThang1009COMMUNITY
Explore all skills by this author →
GitHub

debug

Reproduce bugs, write failing tests, and fix root causes.

15|6|Updated May 7, 2026
Search Tags:#workflow#testing#debugging#reproduce#root-cause#failing-test
One-click install
npx skills add https://github.com/MinhThang1009/dotclaude --skill debug-minhthang1009
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/MinhThang1009/dotclaude/tree/main/plugins/debug/skills/debug
Command: npx skills add https://github.com/MinhThang1009/dotclaude --skill debug-minhthang1009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging workflow: reproduce first, write failing test, then fix. Use when encountering bugs, unexplained errors, or unexpected behavior.

Core Features & Use Cases

  • Step-by-step debugging process to reproduce issues, identify root causes, and verify fixes.
  • Guidance on writing minimal failing tests and integrating them into your workflow.
  • Use case: when a bug is hard to reproduce or presents ambiguous symptoms, follow the steps to isolate the failure.

Quick Start

Reproduce the bug in your local environment, then write a failing test before implementing a fix.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug a bug that is hard to reproduce?▼

To debug a hard-to-reproduce bug, systematically observe symptoms, reproduce the issue locally, form hypotheses, write a failing test, and validate your fix.

What is the best way to fix intermittent test failures in CI?▼

Fix intermittent CI failures by following a structured workflow: reproduce the failing test locally, isolate the root cause, write a minimal failing test, and verify the fix.

Why should I write a failing test before fixing a bug?▼

Writing a failing test before fixing a bug ensures you have successfully reproduced the issue and provides a verifiable baseline to confirm your root-cause fix works.

How do I find the root cause of unexplained errors?▼

Find the root cause of unexplained errors by narrowing down hypotheses through systematic observation and reproduction before implementing and validating your fix.

Can I use a systematic debugging workflow for local development issues?▼

Yes, you can apply this systematic debugging workflow to local development issues by guiding you through observation, reproduction, hypothesis verification, and testing.

What should I do when my software presents ambiguous symptoms?▼

When software presents ambiguous symptoms, follow structured debugging steps to isolate the failure, reproduce the behavior, and write a test before attempting a fix.

Related Skills

Explore More Software Engineering Skills→
proffesor-for-testingproffesor-for-testing
436

bug-reporting-excellence

Create structured bug reports with reproduction steps and environment details.

Community
Advanced
zhouguoqingzhouguoqing
23

debugging

Diagnose failures systematically before changing code.

Community
Intermediate
bostonaholicbostonaholic
8

test-driven-bug-fix

Reproduce, isolate, fix, and verify software defects using test-driven methodology.

Community
Advanced
vzcovzco
15

trace-writes

Trace memory writes in x64 processes using hardware breakpoints and disassembly.

Official
Intermediate