elixir-otp

Elixir and OTP: verify the code path

Workflow

1. Read the repository instructions, .tool-versions, mix.exs, and relevant existing modules/tests. Use its matched Elixir/OTP pair; run elixir --version and mix --version. Do not hardcode another developer's installation path.
2. Read syntax and API examples for matching, guards, strings, maps, pipes, and error handling. Read OTP and integration pitfalls for servers, tasks, configuration, and Ecto.
3. Verify external calls against the installed dependency source or its pinned HexDocs version. Code.ensure_loaded!/1 followed by function_exported?/3 checks functions; use macro_exported?/3 for macros. A missing module is not evidence that its documented API does not exist.
4. Write the smallest implementation following the project's conventions. Use explicit success/error return contracts at boundaries, validate external data, and keep arbitrary input as strings rather than creating atoms.
5. Run mix format --check-formatted, mix compile --warnings-as-errors, and the narrowest relevant mix test test/path_test.exs. Existing unrelated warnings must be reported accurately; a plain compile is not a warning-free check.
6. Exercise both success and failure paths. For OTP changes test the actual process, message ordering, timeout, and shutdown behavior. For persistence, assert a reread observes the change. A mock or compilation alone is not that evidence. Finish by reporting exact commands, outcomes, and uncovered cases.

Snippet verification

From this skill directory, run:

elixir references/verify_snippets.exs SKILL.md references/syntax.md references/gotchas.md

The verifier accepts trusted author-written snippets only; it executes code and is not a sandbox for user-supplied programs. It requires Elixir 1.17 or newer. elixir fences compile with no undefined-call warnings; elixir-run also calls run/0 on defined modules (or executes a wrapped expression); elixir-bad must fail compilation or emit an undefined-call warning. Runtime examples contain assertions, so printing a plausible result is not considered success. Fences must be self-contained; do not depend on definitions in a previous fence.