skills.rest
burnjohn
burnjohnCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify and isolate bug root causes through evidence-based reasoning.

23|24|Updated Oct 7, 2025
Search Tags:#debugging#troubleshooting#diagnostics#code-quality#software-engineering#root-cause-analysis#issue-triage
One-click install
npx skills add https://github.com/burnjohn/quick-blog --skill systematic-debugging-burnjohn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/burnjohn/quick-blog/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/burnjohn/quick-blog --skill systematic-debugging-burnjohn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined framework to identify the true root cause of bugs before attempting fixes, reducing wasted effort and regression risk.

Core Features & Use Cases

  • Gather comprehensive evidence from error messages, logs, and reproducible steps.
  • Form testable hypotheses and validate them with minimal, targeted changes.
  • Document fixes with rationale to ensure accountability and traceability.

Quick Start

Explain the bug you are seeing, gather the exact steps to reproduce, and capture the full error details before proposing any fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I find the root cause of a bug instead of just guessing?▼

To find the root cause of a bug, you must gather comprehensive evidence from error messages and logs, form testable hypotheses, and validate them with minimal, targeted changes before attempting fixes.

What is the best way to troubleshoot intermittent issues and failing tests?▼

Troubleshooting intermittent issues and failing tests requires a structured workflow that enforces evidence-based reasoning, utilizing pattern analysis and hypothesis testing to isolate the true root cause across client, server, and data stores.

How do I start debugging a user-reported bug effectively?▼

To start debugging a user-reported bug, explain the exact steps to reproduce the issue and capture the full error details from logs before proposing or implementing any fix.

Can I use a systematic debugging approach for runtime errors across different platforms?▼

Yes, systematic debugging applies to runtime errors across client, server, and data stores by enforcing evidence gathering and documented fixes with rationale to ensure accountability and traceability.

Why should I document the rationale when fixing code issues?▼

Documenting fixes with rationale ensures accountability and traceability, reducing wasted effort and regression risk by providing a clear record of the root-cause analysis and the reasoning behind the targeted changes.

What are the limitations of fixing bugs without evidence-based reasoning?▼

Fixing bugs without evidence-based reasoning limits your ability to isolate the true root cause, increasing wasted effort and the risk of regressions due to unvalidated hypotheses and untargeted changes.

Related Skills

Explore More Software Engineering Skills→
siviter-xyzsiviter-xyz
21

debugging

Diagnose software defects through structured root-cause analysis and hypothesis testing.

Official
Basic
edgeandnodeedgeandnode

code-test

Run targeted cargo test commands for Rust workspace code changes.

Official
Intermediate
tankpkgtankpkg
1

@tank/bdd-issue-fixer

Automate GitHub issue resolution through BDD workflows and Gherkin scenarios.

Official
Advanced
ybbms777ybbms777
1

bug-reproduction-validator

Reproduce and validate reported software issues to classify them as bugs, user errors, or environmental problems.

Community
Intermediate