debugging

Enforce a four-stage reproduce, locate, fix, and verify debugging workflow.

319|74|Updated May 17, 2025

Search Tags:#testing #debugging #quality-assurance #developer-workflow #reproducibility #root-cause #bug-tracking

Ready to run

npx skills add https://github.com/m-xlsea/ruoyi-plus-soybean --skill debugging-m-xlsea

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/m-xlsea/ruoyi-plus-soybean/tree/main/.claude/skills/debugging
Command: npx skills add https://github.com/m-xlsea/ruoyi-plus-soybean --skill debugging-m-xlsea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a four-stage debugging workflow to prevent ad-hoc debugging and ensure reliable issue resolution.

Core Features & Use Cases

Reproduce: create a minimal, deterministic test case that reliably demonstrates the bug.
Locate: trace the error origin using evidence, logs, and stepping through the call stack rather than guessing.
Fix: address the root cause with targeted changes and accompanying tests.
Verify: run original reproductions and full test suites to confirm no regressions.

Quick Start

In a bug scenario, follow the four stages: reproduce, locate, fix, and verify, documenting inputs, outputs, and decisions at each step.

Frequently Asked Questions about debugging

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

FAQPage Schema

What is the best way to systematically debug software instead of guessing?▼

Systematically debug software by enforcing a four-stage process: reproduce, locate, fix, and verify. This discipline prevents ad-hoc debugging by requiring evidence gathering, documentation, and non-guessing decision making to ensure reliable issue resolution.

How do I locate a root cause bug without guessing the error origin?▼

To locate a root cause bug without guessing, trace the error origin using evidence, logs, and stepping through the call stack. Guardrails prevent skipping stages, enforcing non-guessing decision making and documentation during the locate phase.

How do I create a minimal test case to reliably reproduce a bug?▼

To reliably reproduce a bug, create a minimal, deterministic test case that demonstrates the issue. The reproduce stage mandates documenting inputs, outputs, and decisions to establish a stable baseline before attempting to locate the root cause.

Does this systematic debugging workflow support both frontend and backend scenarios?▼

Yes, this systematic debugging workflow supports common frontend and backend scenarios. It applies evidence gathering, root cause tracing, and validation guardrails uniformly across both environments to ensure reliable issue resolution.

How do I verify a bug fix and prevent regressions in my test suite?▼

To verify a bug fix and prevent regressions, run original reproductions and the full test suite. The verify stage confirms the targeted root cause changes work correctly and ensures no regressions occur across the application.