elixir-code-review

To review Elixir code for OTP best practices, analyze your .ex and .exs source files for correct GenServer and Supervisor usage, proper pattern matching, and adherence to established Elixir coding conventions. This ensures your implementation aligns with core OTP principles.

Elixir documentation standards require modules and functions to be adequately documented with @doc and @spec attributes. Reviewing your source code for these annotations ensures maintainability and helps catch missing type specifications before merging new features.

Yes, you can check .exs and .ex Elixir source files for idiomatic pattern matching. The review process validates that your code follows established Elixir coding conventions and correctly applies pattern matching techniques across your codebase.

You need to review GenServer and Supervisor usage in Elixir before merging new features to ensure OTP best practices are followed. This review catches potential issues related to process management, supervision trees, and pattern matching implementation early.

The best way to ensure Elixir code quality before merging is to run an automated review that checks for idiomatic patterns, OTP basics like GenServer and Supervisor implementation, and documentation standards including @doc and @spec annotations.