domains / families / software-engineering / debugging-and-error-recovery

debugging-and-error-recovery

authentic

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

When to use

• Tests fail after a code change
• The build breaks
• Runtime behavior doesn't match expectations
• A bug report arrives
• An error appears in logs or console
• Something worked before and stopped working

When not to use

• Use this skill only when the task clearly matches its upstream source and local project context.
• Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
• Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Skill page

Source