skills.rest
lywa1998
lywa1998COMMUNITY
Explore all skills by this author →
GitHub

m15-anti-pattern

Detect Rust anti-patterns in source files and suggest idiomatic alternatives.

Updated Jan 21, 2026
Search Tags:#ownership#rust#anti-pattern#code-review#clone#unwrap#idiomatic-rust
One-click install
npx skills add https://github.com/lywa1998/self-host-claude-marketplace --skill m15-anti-pattern-lywa1998
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: m15-anti-pattern
Source: https://github.com/lywa1998/self-host-claude-marketplace/tree/main/plugins/rust-skills/skills/m15-anti-pattern
Command: npx skills add https://github.com/lywa1998/self-host-claude-marketplace --skill m15-anti-pattern-lywa1998

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rust codebases often harbor anti-patterns that cause maintenance headaches, readability issues, and potential safety concerns. This Skill helps reviewers surface these patterns during code reviews, guiding teams toward idiomatic Rust and robust design.

Core Features & Use Cases

  • Anti-pattern detection: Identifies common Rust pitfalls such as excessive cloning, unwrap in production, and improper ownership patterns.
  • Idiomatic refactoring guidance: Provides concrete alternatives and refactor suggestions to improve safety and clarity.
  • Scalable reviews: Applicable to small modules or large crates, enabling both manual reviews and automated checks in CI pipelines.

Quick Start

Review a Rust codebase section and ask the assistant to flag anti-patterns and propose idiomatic replacements.

Frequently Asked Questions about m15-anti-pattern

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

FAQPage Schema
How do I detect Rust anti-patterns like excessive cloning and unwrap in production code?▼

Rust anti-pattern detection involves static analysis of source files to flag excessive clones, unwraps, and improper ownership, generating actionable idiomatic alternatives for code review workflows.

What are common Rust ownership anti-patterns to look for during a code review?▼

Common Rust ownership anti-patterns include excessive cloning, unwrap usage in production, and improper ownership patterns that cause maintenance headaches and potential safety concerns.

How do I refactor Rust code to improve error handling and remove unwrap calls?▼

Refactor Rust error handling by replacing unwrap calls with concrete idiomatic alternatives and improvement suggestions that enhance safety, clarity, and robust design.

Can I use automated Rust anti-pattern checks across large crates in a CI pipeline?▼

Yes, Rust anti-pattern detection is scalable from small modules to large crates, enabling both manual code reviews and automated checks within CI pipelines.

What is the best way to find unnecessary allocations and improper ownership in Rust projects?▼

The best way to find unnecessary allocations and improper ownership is through static analysis that identifies common Rust pitfalls and proposes idiomatic replacements.

Related Skills

Explore More Software Engineering Skills→
Blake-JohnBlake-John

rust-patterns

Enforce idiomatic Rust patterns for ownership, error handling, and concurrency.

Community
Advanced
wangzhongyuan11wangzhongyuan11
1

demo-review-2

Automate Python code review with pylint, bandit, and pytest.

Community
Intermediate
onbjergonbjerg
4

rust

Format and lint Rust code with cargo fmt and cargo clippy.

Community
Intermediate
Ven0m0Ven0m0
4

language-optimization

Optimize Bash, Python, and Rust code with universal principles and language-specific idioms.

Community
Advanced