skills.rest
jasonwilmot
jasonwilmotCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Coordinate a structured debugging workflow to reproduce and resolve software bugs.

Updated Jul 24, 2024
Search Tags:#workflow#debugging#troubleshooting#reproduce#root-cause#isolate
One-click install
npx skills add https://github.com/jasonwilmot/little-riddle --skill debug-jasonwilmot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/jasonwilmot/little-riddle/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/jasonwilmot/little-riddle --skill debug-jasonwilmot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging can be tedious and error-prone without a repeatable workflow; this Skill provides a consistent process to reproduce issues, isolate root causes, hypothesize solutions, verify fixes, and document outcomes.

Core Features & Use Cases

  • Reproduction: capture steps to reliably reproduce bugs across environments.
  • Isolation: identify smallest failing path and environmental factors.
  • Hypothesis & Verification: generate testable hypotheses and verify with evidence.
  • Documentation: maintain traceable root-cause records and fixes for audits.
  • Use Case: When a bug surfaces in CI or prod, follow this workflow to diagnose and resolve it systematically.

Quick Start

Follow the step-by-step debugging workflow to reproduce the issue, document findings, and validate the fix.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug software bugs systematically using a structured workflow?▼

Debugging systematically involves a stepwise, checklist-driven process to reproduce issues, isolate root causes, generate testable hypotheses, verify fixes, and validate results with reproducibility evidence.

What is the best way to reproduce a bug across different environments?▼

Reproducing a bug reliably requires capturing specific steps and environmental factors to trigger the issue consistently. This workflow enforces documentation of reproducibility evidence for traceable root-cause analysis.

How do I isolate the root cause of a production bug?▼

To isolate a root cause, identify the smallest failing path and relevant environmental factors. This structured workflow generates testable hypotheses and verifies them with evidence to pinpoint the exact issue.

Can I use this debugging workflow for issues found in CI and production?▼

Yes, this debugging workflow applies across development and testing phases. When a bug surfaces in CI or production, it guides you through diagnosing and resolving the issue systematically with documented outcomes.

Why do I need a structured workflow for troubleshooting software issues?▼

Troubleshooting without a repeatable workflow is tedious and error-prone. A structured process ensures consistent reproduction, root-cause isolation, hypothesis verification, and documented outcomes for audits and future reference.

Related Skills

Explore More Software Engineering Skills→
liuzhengdongfortestliuzhengdongfortest
1.1k

easysdd-issue-report

Convert informal bug descriptions into YAML-frontmattered markdown issue reports.

Community
Intermediate
haJ1thaJ1t

systematic-debugging

Diagnose bugs to verified root cause using reproduce-minimize-hypothesize-bisect-confirm.

Community
Advanced
cffrankcffrank

visual-qa

Capture Playwright-based screenshots across devices and create UI evidence reports.

Community
Intermediate
a-ariffa-ariff
14

root-cause-tracing

Trace bugs backward from symptoms to identify root causes.

Community
Intermediate