debugging Skills

Evaluate how the logic handles extreme limits. Use when reviewing code for robustness, debugging edge-case failures, or writing tests for critical functions. Activate when a user says "check edge cases", "test boundaries", "what about empty input", "handle extreme values", "does this work with zero", or "what if the list is empty".

State the suspected root cause before writing any code. Use when fixing bugs, resolving errors, or troubleshooting failing tests. Activate when a user says "fix this bug", "why is this broken", "debug this error", "this test is failing", or "something is wrong with". Prevents premature code changes by enforcing hypothesis-driven debugging.

Ensure the data entering the function is the expected shape. Use when debugging unexpected behavior, null reference errors, type errors, or data-related crashes. Activate when a user says "validate inputs", "check the data", "what's being passed in", "wrong data type", "unexpected null", or "the function receives wrong arguments".