elixir-code-review

What This Skill Does

The elixir-code-review skill acts as a specialized static analysis assistant tailored specifically for the Elixir programming language. It leverages idiomatic best practices, functional programming principles, and OTP (Open Telecom Platform) standards to provide actionable feedback on your codebase. By analyzing .ex and .exs files, the skill ensures that your code is not just functional, but also maintainable, performant, and secure. It checks for common pitfalls such as improper pattern matching, blocking operations in GenServers, missing documentation, and potential security vulnerabilities like atom-injection from user input.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/anderskev/elixir-code-review Once installed, the skill will automatically monitor your workspace files and activate whenever you initiate a review session for Elixir source files.

Use Cases

This skill is ideal for:

• Senior developers enforcing team-wide code standards across large umbrella projects.
• Junior developers seeking feedback on their implementation of complex OTP processes or recursion patterns.
• Teams performing pre-commit security audits on applications that process external user inputs.
• Refactoring sessions where you need to transition from imperative-style case statements to idiomatic with clauses or function-head pattern matching.

Example Prompts

1. "Analyze this GenServer implementation for potential blocking calls and ensure the handle_continue implementation is efficient."
2. "Review the current module for pattern matching improvements; can these nested case statements be refactored into private functions?"
3. "Check this entire file for missing @spec tags and ensure all public functions have valid @doc documentation."

Tips & Limitations

To maximize the utility of the elixir-code-review skill, always ensure your project is up-to-date with your current dependency tree. While the skill is excellent at identifying patterns, it is a static analyzer and cannot always predict complex runtime behavior in highly dynamic systems. It is best used as a supplement to dialyzer and standard credo checks. Always run the verification protocol before applying refactors suggested by the agent to ensure logic parity.