← ClaudeAtlas

debug-errorlisted

Systematically debug and fix errors using structured investigation. Use when the user asks to "debug", "fix an error", "troubleshoot", "investigate a bug", or shares an error message or stack trace.
drafael/coding-harness · ★ 1 · Code & Development · score 77
Install: claude install-skill drafael/coding-harness
# Systematically Debug and Fix Errors Systematically debug and fix errors. ## Instructions Follow this comprehensive debugging methodology to resolve: **$ARGUMENTS** 1. **Error Information Gathering** - Collect the complete error message, stack trace, and error code - Note when the error occurs (timing, conditions, frequency) - Identify the environment where the error happens (dev, staging, prod) - Gather relevant logs from before and after the error 2. **Reproduce the Error** - Create a minimal test case that reproduces the error consistently - Document the exact steps needed to trigger the error - Test in different environments if possible - Note any patterns or conditions that affect error occurrence 3. **Stack Trace Analysis** - Read the stack trace from bottom to top to understand the call chain - Identify the exact line where the error originates - Trace the execution path leading to the error - Look for any obvious issues in the failing code 4. **Code Context Investigation** - Examine the code around the error location - Check recent changes that might have introduced the bug - Review variable values and state at the time of error - Analyze function parameters and return values 5. **Hypothesis Formation** - Based on evidence, form hypotheses about the root cause - Consider common causes: - Null pointer/undefined reference - Type mismatches - Race conditions - Resource exhaustion - Lo