elixir-dev

What This Skill Does

The elixir-dev skill is a comprehensive development companion tailored for the Elixir programming language and the Phoenix web framework. It acts as an expert pair programmer capable of executing, interpreting, and debugging common Mix tasks. The skill handles the full lifecycle of Elixir development, including running and diagnosing test failures, performing static code analysis with Credo, ensuring type safety via Dialyzer, and maintaining code style with the built-in formatter. Beyond CLI operations, it provides deep architectural support for OTP patterns, guiding users through the creation of context modules, Ecto schemas, GenServers, and supervisors while enforcing industry best practices like documentation and specification annotations.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/gchapim/elixir-dev

Use Cases

Use this skill when you are:

• Writing new business logic in Phoenix context modules.
• Debugging complex Ecto changesets or troubleshooting DBConnection.OwnershipError in your test suite.
• Refining code quality to meet strict Credo standards or fixing compilation warnings.
• Implementing OTP behaviors such as supervisors or GenServers for background task management.
• Refactoring existing codebases to align with modern Elixir conventions, ensuring all public functions have @doc and @spec tags.

Example Prompts

1. "I am getting a MatchError in my Accounts context. Here is the code [code snippet]; can you identify why the return value shape is incorrect?"
2. "Help me write an Ecto migration to add a user_id foreign key to the notifications table, then generate the corresponding schema file with appropriate timestamps and validations."
3. "My Dialyzer run is failing with 'The call will never return'. Look at my process_payment/1 function and suggest how to fix the typespecs or handle the error cases properly."

Tips & Limitations

To maximize the utility of this skill, always provide the full context of your modules, including imports and aliases. When debugging test failures, include the stack trace provided by your shell. Note that while this skill can format your code and suggest fixes, it is designed as a companion; always review suggested refactors before applying them to your production codebase to ensure logical consistency.