gleam-review

name	gleam-review
description	Review Gleam code against the official Gleam conventions, patterns, and anti-patterns guide. Identifies anti-patterns (check-then-assert, catch-all matches, panicking in libraries, abbreviations, fragmented modules), convention violations (unqualified imports, missing type annotations, fallible functions that don't return Result), and opportunities to apply recommended patterns (descriptive errors, invalid-states-impossible modelling, builder pattern). Manual invocation only — run via /gleam-review, optionally with files, directories, or package names as arguments.
disable-model-invocation	true

Gleam Code Review

Review Gleam code against the official Gleam style guide. The full guide is in references/conventions.md — read it in its entirety before reviewing, every time. It is the authority for this review; do not substitute general functional-programming intuitions for what it actually says.

This is a review, not a refactor: report findings and stop. Only apply fixes if the user asks for them afterward.

Determine scope

Use the first of these that applies:

1. Arguments were given (file paths, directories, or package names) — review those. A bare name like lattice_core means that package's src/ and test/ directories.
2. There are uncommitted changes — review the changed .gleam files (git status / git diff).
3. The current branch differs from main — review the .gleam files changed on the branch (git diff main...HEAD --name-only).
4. Otherwise, ask the user what to review.