When should I use the m06-error-handling skill?

Invoke this skill whenever you are designing error types, handling potential failures in logic, or refactoring code to improve its stability and crash-resistance.

Can this skill help with error context?

Absolutely. it emphasizes the use of .context() and mapping error types to ensure that callers have enough information to handle or log the failure effectively.

Does this skill distinguish between library and application code?

Yes, it provides specific guidance on using 'thiserror' for typed library errors and 'anyhow' for ergonomic application-level error management.

How does this help with 'unwrap' panics?

The skill provides a framework to determine if a failure is truly a bug (where panic is acceptable) or an expected outcome that should be handled with Result or Option.

Rust Error Handling Strategy

Name: Rust Error Handling Strategy
Author: actionbook

byactionbook

•

596

API Development

Optimizes Rust codebases by implementing robust error handling patterns and architectural decision-making frameworks.

About

This skill provides a meta-problem-driven knowledge index that enables Claude to navigate complex Rust error handling scenarios. It helps distinguish between expected failures and bugs, guiding the implementation of Result, Option, and panic strategies. By applying this skill, developers ensure their Rust projects follow ecosystem best practices, such as utilizing thiserror for libraries and anyhow for applications, while maintaining clear error propagation and contextual debugging information.

Key Features

Systematic error propagation patterns using the '?' operator and context injection
Decision flowcharts for choosing between Result, Option, and panic!
596 GitHub stars
Anti-pattern identification for unwrap, expect, and silent error ignoring
Context-aware crate selection (thiserror vs. anyhow) based on project scope
Domain-specific error design guidance for production-grade reliability

Use Cases

Standardizing error context and logging across large-scale Rust applications
Refactoring code to replace dangerous .unwrap() calls with safe error propagation
Designing custom error types for new Rust libraries using thiserror

About

Key Features

Systematic error propagation patterns using the '?' operator and context injection
Decision flowcharts for choosing between Result, Option, and panic!
596 GitHub stars
Anti-pattern identification for unwrap, expect, and silent error ignoring
Context-aware crate selection (thiserror vs. anyhow) based on project scope
Domain-specific error design guidance for production-grade reliability

Use Cases

Standardizing error context and logging across large-scale Rust applications
Refactoring code to replace dangerous .unwrap() calls with safe error propagation
Designing custom error types for new Rust libraries using thiserror