m15-anti-pattern

Detect and refactor common Rust anti-patterns during code review.

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/simorgh3196/tsuzulint --skill m15-anti-pattern
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: m15-anti-pattern
Source: https://github.com/simorgh3196/tsuzulint/tree/main/.agents/skills/m15-anti-pattern
Command: npx skills add https://github.com/simorgh3196/tsuzulint --skill m15-anti-pattern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers identify and avoid common Rust anti-patterns during code review, improving reliability and readability.

Core Features & Use Cases

  • Pattern detection: Recognizes common Rust anti-patterns such as overuse of clone, unwrap everywhere, unnecessary boxing, and poor error handling.
  • Guided refactoring: Provides recommended idiomatic replacements and best practices for maintainable code.
  • Code-review scenarios: Useful during peer reviews, onboarding, and learning Rust idioms.

Quick Start

Use the m15-anti-pattern guide to review a Rust project and apply the recommended idiomatic improvements.

Frequently Asked Questions about m15-anti-pattern

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify and fix common Rust anti-patterns during code review?

To identify Rust anti-patterns during code review, look for overuse of clone, unwrap in production, unnecessary boxing, and poor error handling, then apply idiomatic replacements for ownership and error management to refactor smarter.

What are idiomatic Rust replacements for excessive cloning and unwrap usage?

Idiomatic Rust replaces excessive cloning with proper ownership borrowing and replaces unwrap in production with robust error handling, providing concrete refactoring guidance to improve code reliability and readability.

How do I refactor Rust code to improve ownership and error handling?

Refactor Rust code by mitigating unnecessary boxing and poor error handling, applying concrete idiomatic replacements across ownership and error handling boundaries to ensure maintainable and reliable code.

When should I avoid using unwrap in production Rust applications?

Avoid using unwrap in production Rust applications to prevent runtime panics, applying guided error handling refactoring instead to safely manage expected failures and improve overall code reliability.

Does this Rust anti-pattern detection cover ownership and boxing issues?

Yes, Rust anti-pattern detection covers ownership and boxing issues by recognizing unnecessary boxing and clone overuse, providing recommended idiomatic replacements and best practices for maintainable code.