Error Handling

This skill is guidance, not a script. Define failures, their owners, and what remains safe after failure.

When not to use

• Diagnosing a wrong behavior or a failure with an unclear cause. Use debug.
• Test isolation for asynchronous cleanup and teardown. Use test-reliability.
• The wording of a report. Use prose-standard.

Inputs and authorization

• Required: the failure path or operation in scope. If it is missing, report it and stop.
• Authorization: a review is read-only. Change behavior only when the task asks for a fix. A behavior or compatibility change needs renewed alignment.

Method

Classify the failure