Diagnose failures from runtime evidence before editing code.
Scanned 9/1/2026
Install to Claude Code
Skills Directorynpx -y skills add amplifthq/oh-my-dsh --skill systematic-debugging --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Systematic Debugging?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/amplifthq-systematic-debugging)More formats (shields.io, HTML) on the badges page.
---
name: systematic-debugging
description: Diagnose failures from runtime evidence before editing code.
whenToUse: Use for bugs, test failures, crashes, hangs, and unexpected behavior.
---
# Systematic debugging
1. Reproduce the exact symptom with the smallest safe command.
2. Capture the complete error, inputs, environment, and boundary where expected behavior diverges.
3. Form one falsifiable hypothesis at a time and test it with focused instrumentation or an existing diagnostic.
4. Follow values backward to the first incorrect state; do not patch the last visible exception unless it is the cause.
5. Add or identify a regression check that fails for the original bug.
6. Make the smallest causal fix, rerun the regression check, then run proportionate surrounding checks.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
