m15-anti-pattern

Identifying Rust anti-patterns during code review involves scanning for patterns like excessive cloning, unwrap in production, and misused Rc that erode safety, readability, and maintainability. This skill provides a structured checklist to rapidly spot these ownership and error-handling pitfalls across library and application code.

Refactoring Rust code with excessive cloning and unwrap usage requires guided prompts with concrete steps to rewrite problematic code safely. This skill provides structured trace-up and trace-down pointers alongside best practices to replace panics and ownership pitfalls with idiomatic Rust improvements.

Yes, this anti-pattern checklist can be applied to both library and application Rust codebases. It is designed to inspect Rust modules during code reviews, covering ownership and error-handling scenarios regardless of whether the code is library or application logic.

Misused Rc causes ownership pitfalls in Rust by introducing unnecessary reference counting when ownership can be restructured more safely. This skill helps spot misused Rc anti-patterns and provides guided refactoring prompts to rewrite the code for safer, idiomatic Rust improvements.

Fixing frequent Rust panics caused by unwrap in production code involves identifying these anti-patterns and applying structured refactoring guidance. This skill offers a comprehensive catalog to spot unwrap usage and proposes safe, idiomatic error-handling alternatives instead of panicking.

You should avoid using Rc in Rust when standard ownership transfers or references can achieve the same result without reference counting overhead. This skill helps identify these misused Rc anti-patterns during code reviews and provides guidance to refactor toward safer, idiomatic ownership models.