debug-methodology
abczsl520 द्वारा
Coding Agents & IDEsसंक्षिप्त
Systematic debugging that prevents patch-chaining and workaround addiction in AI agents.
विवरण
यह स्किल क्या करती है
A structured debugging approach built around root cause analysis. Forces a stop-and-assess phase before any fix attempt, enforces the 5 Whys for non-obvious bugs, and cuts off patch-chaining after two failed attempts. Distinguishes genuine fixes from workarounds using a concrete self-check test.
Most debugging approaches describe process steps but don't enforce a gate that blocks workarounds before they get applied, which is where patch-chains start.
इसे कब इस्तेमाल करें
- Debugging a recurring API timeout that keeps returning after each fix attempt
- Stopping a chain of failed deployment fixes before the codebase degrades further
- Verifying a proposed patch targets root cause before pushing to production
- Tracing a regression to a specific recent code change
- Safely modifying and redeploying server files without breaking the running service
उदाहरण वर्कफ़्लो
User asks: Our API keeps returning 524 timeout errors and switching to a faster model didn't help
- 1
Stop and record the exact symptom: Cloudflare 524 after connections exceed 100 seconds
- 2
Apply Root Cause Gate: switching models is a workaround, not a fix, because the timeout occurs regardless of model speed
- 3
Run 5 Whys: 524 → connection held >100s → server sends no data during processing → non-streaming fetch used → streaming API not implemented
- 4
Propose root cause fix: switch to streaming API so Cloudflare receives continuous data and does not cut the connection
- 5
Verify post-fix: confirm 524 errors stop, check for regressions, confirm removing streaming reproduces the timeout
Streaming API implemented, 524 errors resolved, root cause documented
इंस्टॉलेशन
clawhub install abczsl520/debug-methodologyCLI कमांड चलाएँ, या प्रॉम्प्ट को Claude Code, Cursor, Codex या जो भी कोडिंग एजेंट आप इस्तेमाल करते हैं उसमें पेस्ट करें।