| name | Debug Loop |
| description | Structured debugging workflow. Use when errors, failing tests, broken builds, unexpected model/provider failures, runtime crashes, or flaky behavior appear. |
| allowed-tools | Read, Bash, Edit, MultiEdit |
Debug Loop
Use this skill to debug without guessing.
Process
- Reproduce or locate exact failure: command, log line, stack trace, status code, timestamp.
- Identify boundary: app code, dependency, environment, provider, config, network, data.
- Form one hypothesis at a time.
- Inspect smallest relevant files/logs.
- Patch minimally.
- Re-run the same failing check.
- Add a regression test or guard when feasible.
Rules
- Do not mask errors with broad catch blocks.
- Do not delete state/cache unless evidence points there.
- Do not change unrelated config.
- If provider/model issue, capture finish reason, status, provider, tokens, latency, and retry behavior.