elm-code-review

Review Elm code for idiomatic patterns, TEA, and module organization.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/bromanko/llm-agents --skill elm-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elm-code-review
Source: https://github.com/bromanko/llm-agents/tree/main/skills/elm-code-review
Command: npx skills add https://github.com/bromanko/llm-agents --skill elm-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for consistent, high-quality Elm code by providing automated checks for idiomatic patterns, The Elm Architecture, and clean module design.

Core Features & Use Cases

  • Idiomatic Pattern Analysis: Ensures code adheres to Elm's best practices.
  • The Elm Architecture (TEA) Validation: Checks for correct implementation of Model, Msg, update, and view.
  • Module Organization Review: Assesses clarity and structure of Elm modules.
  • Use Case: A team can use this Skill to maintain a high standard of code quality across their Elm projects, catching potential issues early in the development cycle.

Quick Start

Use the elm-code-review skill to analyze the provided Elm code for quality and adherence to best practices.

Frequently Asked Questions about elm-code-review

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

FAQPage Schema
How do I review Elm code for adherence to The Elm Architecture and idiomatic patterns?

Review Elm code by analyzing TEA implementation, type design, and module organization. Check Model, Msg, update, and view structures against idiomatic patterns to ensure adherence to best practices.

What does an Elm code quality checklist cover for type safety and JSON handling?

An Elm code quality checklist covers type design, Maybe/Result handling, pattern matching, and JSON decoding. It assesses naming conventions, pipeline usage, and module structure to identify issues with severity levels.

Can I use an automated tool to catch Elm refactoring issues and enforce best practices?

Yes, automated tools can catch Elm refactoring issues by evaluating code against a detailed checklist. They identify clarity problems, pipeline usage, and module organization issues, providing actionable suggestions for improvement.

How do I assess Elm module organization and naming conventions in my project?

Assess Elm module organization by reviewing module structure, naming conventions, and clarity. Analyze code against best practices to ensure clean module design and identify organizational issues with actionable suggestions.

What is the best way to validate Maybe and Result handling in Elm code?

Validate Maybe and Result handling by reviewing pattern matching and type safety in Elm code. Analyze how these types are managed against idiomatic patterns to identify potential issues and suggest improvements.

Why does my Elm code review flag HIGH severity issues for TEA implementation?

Elm code review flags HIGH severity issues when The Elm Architecture implementation is incorrect. It checks Model, Msg, update, and view structures against idiomatic patterns to identify critical deviations from best practices.