When reviewing Rust code, certain patterns can hide deeper problems. This guide helps you spot common mistakes like overusing .clone() or .unwrap() in production code. It shows you better ways to write clean and safe Rust.
Anyone doing code reviews will find this useful. It lists top beginner mistakes and gives clear fixes. Use it to catch code smells early and guide your team toward idiomatic Rust.
Global
mkdir -p ~/.claude/skills/m15-anti-patternProject
mkdir -p .claude/skills/m15-anti-patternSource Repository
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Auditpbakaus/impeccable
Audit your code for accessibility performance theming and anti-patterns
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues