Standardize Elixir code style, testing, and error handling with OTP and mix tooling.
npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-ex
Please help me install this Agent Skill. Skill: lang-ex Source: https://github.com/dragoscirjan/opencode-config/tree/main/skills/lang-ex Command: npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-ex
This Skill gives Elixir developers a compact set of standards for writing consistent, maintainable code and choosing the right tooling.
Use it when you need a shared baseline for code reviews, refactors, new feature implementation, or team conventions in an Elixir codebase.
Ask the assistant to apply the lang-ex skill to review or write Elixir code using the repo's conventions.
High-intent search queries and answers about installing and using this skill.
Establish Elixir coding standards by adhering to the Elixir Style Guide, running mix format, and enforcing Credo lints. This standardizes OTP supervision tree conventions, pattern matching in function heads, and tuple-based error handling for maintainable application development.
The best way to set up Elixir code review conventions is to establish a shared baseline using the Elixir Style Guide, mix format, Credo, Dialyxir, and ExUnit. This provides consistent rules for pipe chains, pattern matching, and OTP architecture during refactors and new feature implementation.
Yes, this Elixir guidance directly integrates with mix-based tooling by requiring mix format, Credo, Dialyxir, and ExUnit. It reinforces using these tools for formatting, static analysis, linting, and testing to maintain code quality and reliable supervision-tree conventions.
Standardize Elixir error handling by enforcing tuple-based error returns and adhering to OTP supervision tree conventions. Applying these architecture rules ensures resilient application implementation and reliable error recovery during development and refactoring tasks.
You should use Credo and Dialyxir to enforce quality gates that catch style violations and type errors during Elixir development. Combined with mix format and ExUnit, they ensure code meets Elixir Style Guide standards for consistent, maintainable application architecture.
barnabasJProvide Elixir coding standards for Phoenix, Ecto, Ash, and OTP workflows.
jg-chalk-ioEncapsulate OTP, LiveView, and deployment patterns for Elixir and Phoenix applications.
DecoyLexRun mix format, Credo linting, and test reviews on Elixir codebases.
deandumEnforce language-agnostic coding style and conventions across a codebase.
