m15-anti-pattern

To identify Rust anti-patterns during code review, surface clones, unwraps, Rc usage, and unsafe blocks that mask ownership or error-handling issues. The skill catalogs these smells and maps each to better patterns with clear reasons why they hurt maintainability.

Common Rust code smells include unnecessary clones, unwrap calls, Rc usage, and unsafe blocks. These patterns mask underlying ownership or error-handling issues, and recognizing them helps prevent flawed design from propagating through your codebase.

Trace Rust clone and unwrap usage back to design issues by following trace up and trace down prompts. These connect symptoms to higher-level design skills such as ownership modeling, domain flow, or error handling to restart the design conversation.

Yes, this skill helps review unsafe blocks and Rc usage in Rust by flagging them as suspicious patterns. It explains why these smells hurt maintainability and suggests next diagnostic steps to trace ownership, error handling, or domain issues.

The best way to catch beginner mistakes in Rust peer review is using a review checklist of top code smell indicators and refactoring nudges. This stamps out flawed patterns by highlighting clones, unwraps, and other suspicious usage during review.

You should avoid clone and unwrap in Rust when they mask ownership or error-handling design issues. These patterns often indicate flawed design choices that hurt maintainability and should be traced to higher-level domain or ownership problems.