lang-ex

Standardize Elixir code style, testing, and error handling with OTP and mix tooling.

Updated Mar 19, 2026

Search Tags:#elixir #coding-standards #otp #exunit #credo #mix #dialyxir

Ready to run

npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-ex

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives Elixir developers a compact set of standards for writing consistent, maintainable code and choosing the right tooling.

Core Features & Use Cases

Style Guidance: Favors the Elixir Style Guide, pipe chains, and pattern matching in function heads.
Quality Gates: Encourages mix format, Credo, Dialyxir, and ExUnit for formatting, linting, static analysis, and tests.
Architecture Rules: Reinforces tuple-based error handling and OTP supervision for resilient applications.

Use it when you need a shared baseline for code reviews, refactors, new feature implementation, or team conventions in an Elixir codebase.

Quick Start

Ask the assistant to apply the lang-ex skill to review or write Elixir code using the repo's conventions.

Frequently Asked Questions about lang-ex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce Elixir coding standards for OTP and pattern matching in my project?▼

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.

What is the best way to set up Elixir code reviews and refactoring conventions?▼

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.

Does this Elixir guidance work with mix-based tooling and ExUnit testing?▼

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.

How do I handle Elixir error handling and supervision tree conventions consistently?▼

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.

Why should I use Credo and Dialyxir for Elixir static analysis and linting?▼

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.