error-handling

Anveio's avatarfrom Anveio

Error-handling conventions (error mapping/presentation, what to throw vs return, user-facing output). Use when adding errors or changing failure behavior.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 17, 2025⬇️2downloads

When & Why to Use This Skill

This Claude skill streamlines software development by enforcing consistent error-handling conventions, including error mapping, user-facing message standardization, and exit code management. It ensures that failure behaviors are predictable and align with repository-specific documentation, significantly improving code maintainability, system reliability, and the end-user experience.

Use Cases

  • Standardizing Error Shapes: Implementing a consistent error response structure across multiple microservices or internal packages to ensure architectural uniformity.
  • User-Facing Output Mapping: Translating complex internal system exceptions into clear, actionable, and localized messages for end-users.
  • CLI Exit Code Configuration: Defining and implementing standardized exit codes for command-line tools to facilitate reliable automation and integration with CI/CD pipelines.
  • Convention Alignment: Updating legacy codebases to comply with internal error-handling guidelines (e.g., docs/error-handling.md) during refactoring or when adding new features.
nameerror-handling
descriptionError-handling conventions (error mapping/presentation, what to throw vs return, user-facing output). Use when adding errors or changing failure behavior.

Error Handling

When to use

Use this when the task mentions:

  • error mapping, user-facing messages, exit codes
  • “how should this failure be surfaced”
  • standardizing error shapes across packages

Canonical repo doc

Read your repo’s error-handling conventions doc (commonly docs/error-handling.md).