Agent skill · software engineering · aiskillstore
debugging
Systematically debug code issues using proven methodologies. Use when encountering errors, unexpected behavior, or performance problems. Handles error analysis, root cause identification, debugging strategies, and fix verification.
Why this skill is useful
Codifies systematic debugging methodologies and strategies that the AI could infer but now doesn't have to guess.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Debugging When to use this skill Encountering runtime errors or exceptions Code produces unexpected output or behavior Performance degradation or memory issues Intermittent or hard-to-reproduce bugs Understanding unfamiliar error messages Post-incident analysis and prevention Instructions Step 1: Gather Information Collect all relevant context about the issue: Error details: Full error message and stack trace Error type (syntax, runtime, logic, etc.) When did it start occurring? Is it reproducible? Environment: Language and version Framework and dependencies OS and runtime environment Recent changes to code or config Step 2: Reproduce the Issue Create a minimal, reproducible example: Step 3: Isolate the Problem Use binary search debugging to narrow down the issue: Print/Log debugging: Divide and conquer: Step 4: Analyze Root Cause Common bug patterns and solutions: Pattern Symptom Solution --------- --------- ---------- Off-by-one Index out of bounds Check loop bounds Null reference NullPointerException Add null checks Race condition Intermittent failures Add synchronization Memory leak Gradual slowdown Check resource cleanup Type mismatch Unexpected behavior Validate types Questions to ask: 1. What changed recently? 2. Does it fail with specific inputs? 3. Is it environment-specific? 4. Are there any patterns in failures? Step 5: Implement Fix Apply the fix with proper verification: Fix checklist: [ ] Addresses root cause, not just symptom [ ] Doesn't break existing functionality [ ] Handles edge cases [ ] Includes appropriate error handling [ ] Has test coverage Step 6: Verify and Prevent Ensure the fix works and prevent regression: Examples Example 1: TypeError debugging Error: Analysis: Example 2: Race condition debugging Symptom: Test passes locally, fails in CI intermittently Analysis: Example 3: Memory leak debugging Tool: Use memory profiler Best practices 1. Reproduce first: Never fix what you can't reproduce 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/debugging--0baed5