Error Handling Patterns
Decides which failures are values and which are exceptions.
Install
/plugin marketplace add wshobson/agents; /plugin install developer-essentials
When error handling is being designed for a feature, an API surface, or a distributed call path.
- Author
- wshobson
- License
- MIT
The skill separates expected failures — validation, a rejected payment, a rate limit — from genuinely exceptional ones, and picks the mechanism accordingly: Result and Option types for the first, exceptions for the second, a hard stop for programmer bugs. Around that it covers retries, circuit breakers and graceful degradation for calls that cross a network boundary. Context preservation runs through all of it, since an error that loses its stack and its metadata costs more in debugging than it saved in code.
Similar skills
Error Debugging
SkillWorks backward from a symptom to the release that caused it, then writes the query catching a repeat.
Systematic Debugging
SkillForces reproduce-first debugging instead of speculative patching
Debugging and Error Recovery
SkillStops the line on an unexpected error and works down to the root cause.
Comments(0)
Sign in to comment