Why does it flag map[:key] usage?

The skill encourages 'assertive map access' (map.key) for required keys to ensure the application fails fast with clear errors instead of propagating nil values silently.

How does this skill help with Elixir security?

It detects dangerous patterns like uncontrolled dynamic atom creation which can lead to memory exhaustion and Denial of Service (DoS) attacks on the Erlang VM.

Can it refactor complex error handling?

Yes, it specifically identifies bloated 'else' blocks in 'with' statements and suggests normalizing return types in private functions for better clarity.

What is Namespace Trespassing in Elixir?

Namespace Trespassing occurs when a library defines modules outside its own namespace, risking conflicts. This skill identifies these cases and suggests proper prefixing.

Elixir Anti-Pattern Refactor

Name: Elixir Anti-Pattern Refactor
Author: vinnie357

byvinnie357

Security & Testing

Identifies and refactors common Elixir code smells and design anti-patterns into idiomatic, performant code.

About

This skill empowers Claude to act as an expert Elixir mentor by detecting non-idiomatic patterns and providing production-grade refactoring suggestions. It targets specific issues common in Elixir development, such as complex error handling in 'with' blocks, dangerous dynamic atom creation, and 'Namespace Trespassing'. By applying these best practices, developers can improve the maintainability, security, and performance of their Elixir applications while ensuring they leverage the full power of the Erlang VM.

Key Features

Provides idiomatic replacements for excessive comments and primitive obsession.
Identifies security risks like uncontrolled dynamic atom creation from untrusted input.
Refactors non-assertive pattern matching and boolean logic into cleaner constructs.
Detects complex error handling in 'with' statements and suggests normalization.
0 GitHub stars
Flags 'Namespace Trespassing' to prevent module naming conflicts across libraries.

Use Cases

Modernizing legacy Elixir codebases by replacing anti-patterns with idiomatic alternatives.
Conducting automated code reviews to enforce community best practices.
Hardening application security by identifying improper atom conversion and data extraction.

About

Key Features

Provides idiomatic replacements for excessive comments and primitive obsession.
Identifies security risks like uncontrolled dynamic atom creation from untrusted input.
Refactors non-assertive pattern matching and boolean logic into cleaner constructs.
Detects complex error handling in 'with' statements and suggests normalization.
0 GitHub stars
Flags 'Namespace Trespassing' to prevent module naming conflicts across libraries.

Use Cases

Modernizing legacy Elixir codebases by replacing anti-patterns with idiomatic alternatives.
Conducting automated code reviews to enforce community best practices.
Hardening application security by identifying improper atom conversion and data extraction.