debug

Diagnose and fix software bugs through a reproducible debugging workflow.

5.5k|794|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/shiaho777/web-to-app --skill debug-shiaho777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/shiaho777/web-to-app/tree/main/app/src/main/assets/skills/debug
Command: npx skills add https://github.com/shiaho777/web-to-app --skill debug-shiaho777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers quickly identify, reproduce, and fix bugs in a project, reducing debugging time and guesswork.

Core Features & Use Cases

  • Structured diagnosis: follows a step-by-step workflow to read symptoms, reproduce paths mentally, form falsifiable hypotheses, and verify fixes.
  • Root-cause focus: prioritizes root causes over symptomatic patches to ensure robust, lasting stability.
  • Collaborative verification: guides testing and documentation to ensure changes are verifiable and repeatable.

Quick Start

Describe the symptom and follow the step-by-step method to reproduce, diagnose, fix, and verify the bug.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I diagnose and fix a bug using a structured debugging workflow?

To fix a bug effectively, use a structured workflow to read symptoms, reproduce paths mentally, form falsifiable hypotheses, verify with code inspection, and validate the fix. This reduces guesswork and debugging time.

What is the best way to find the root cause of an intermittent backend crash?

The best way to find a root cause is to prioritize deep code analysis over symptomatic patches. Form a falsifiable hypothesis, inspect the code to verify the error path, and apply a fix that ensures robust, lasting stability.

Can I use a structured diagnosis method for both frontend and backend code errors?

Yes, structured diagnosis is applicable to user-reported errors, crashes, and intermittent behavior across both frontend and backend code during development and testing, ensuring changes are verifiable and repeatable.

How do I reproduce a user-reported error path when debugging a software project?

To reproduce an error path, start by reading the reported symptoms and tracing the execution path mentally. This step-by-step method helps you form a hypothesis and verify the exact conditions triggering the bug.

Why should I form a falsifiable hypothesis before applying a bug fix?

Forming a falsifiable hypothesis ensures you target the actual root cause rather than applying a symptomatic patch. It guides your code inspection to verify the failure path before you implement and validate the fix.