← ClaudeAtlas

systematic-debugginglisted

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Observe the failure first. Do not use it to implement an already-approved design, to add a feature with no failing behavior, or to guess a root cause from a one-line complaint.
willy92wins/DayZ-Modding-Knowledge-Pack · ★ 25 · Code & Development · score 78
Install: claude install-skill willy92wins/DayZ-Modding-Knowledge-Pack
# Systematic Debugging ## Overview **Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure. **Violating the letter of this process is violating the spirit of debugging.** ## The Iron Law ``` NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST ``` If you haven't completed Phase 1, you cannot propose fixes. ## When to use Use for a technical failure you can name: test failures, production bugs, unexpected behavior, performance problems, build failures, integration issues. **Use this ESPECIALLY when:** - Under time pressure (emergencies make guessing tempting) - "Just one quick fix" seems obvious - You've already tried multiple fixes - Previous fix didn't work - You don't fully understand the issue **Don't skip when:** - Issue seems simple (simple bugs have root causes too) - You're in a hurry (rushing guarantees rework) - Manager wants it fixed NOW (systematic is faster than thrashing) **Do not use this to:** - Implement an already-approved design (that is implementation, not debugging) - Add a feature that has no failing behavior - Rewrite architecture on the first failure - Produce a postmortem, a status update, or a blame assignment ## Intake — before Phase 1 You need three things. Nothing else starts. Do not form a hypothesis, do not add instrumentation, do not propose a fix. 1. **A named failure.** An error message, a failing test, a broken behavior, a measured regression. "Something's wrong" or "the app is weird" is not enou