elm-test-review

Analyze Elm test code for coverage gaps, edge cases, and quality.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of ensuring robust and comprehensive test suites for Elm applications, identifying gaps in coverage, and improving the overall quality and maintainability of tests.

Core Features & Use Cases

  • Test Coverage Analysis: Identifies untested public functions and critical code paths.
  • Test Quality Assessment: Evaluates tests against best practices for clarity, focus, and determinism.
  • Edge Case Identification: Pinpoints scenarios and custom type variants that are not adequately covered.
  • Use Case: A developer wants to ensure their new Elm feature is thoroughly tested before release. They use this skill to get a detailed report on any missing tests, potential edge cases, and suggestions for improving existing test quality.

Quick Start

Run /review elm test to start an interactive test review for your Elm project.

Frequently Asked Questions about elm-test-review

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

FAQPage Schema
How do I find missing edge cases in my Elm test suite?

Elm test review identifies missing edge cases by mapping source files to tests and assessing coverage of custom type variants. It generates a structured Markdown report highlighting untested scenarios and skipped tests with severity indicators.

What is the best way to analyze Elm test coverage for working changes?

Analyzing Elm test coverage for working changes involves scoping the review to modified files, mapping source code to existing tests, and evaluating assertion patterns. The resulting report identifies untested public functions and critical code paths.

How do I check Elm test quality and adherence to best practices?

Checking Elm test quality requires evaluating tests against best practices for clarity, focus, and determinism. A review tool assesses assertion patterns and skipped tests, providing findings in a structured Markdown format with severity indicators.

Can I review specific Elm test files instead of the entire project?

Yes, you can scope the Elm test review based on user-specified files or working changes. This allows the analysis to target specific source-to-test mappings, coverage gaps, and edge case handling within the selected scope.

What does an Elm test coverage report include?

An Elm test coverage report includes findings on coverage gaps, missing edge cases, skipped tests, and assertion patterns. Results are presented in a structured Markdown format with severity indicators to highlight test quality issues.

Why are my Elm tests passing but still missing critical code paths?

Passing Elm tests may still miss critical code paths if untested public functions or unhandled custom type variants exist. A test review maps source to tests to pinpoint these coverage gaps and inadequate edge case handling.