Verify Elixir/Phoenix changes – compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
Verify Elixir/Phoenix changes - compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.This is the skill's description: the text your AI reads to decide when the skill applies.
elixir-verify/SKILL.md
---
name: phx:verify
description: Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
effort: low
---
# Verification Loop
Project-aware verification for Elixir/Phoenix. Reads `mix.exs` and `.check.exs` to discover tools, test commands, and custom aliases before running anything.
## Iron Laws
1. **Discover before running** — Read `mix.exs` first; never run `mix credo` if credo isn't a dependency
2. **Prefer ex_check** — If `:ex_check` + `.check.exs` exists, `mix check` replaces individual steps
3. **Prefer project aliases** — If `mix ci` or composite alias exists, use it over individual steps
4. **Run in order** — Later steps assume earlier ones pass
5. **Ask before E2E tests** — Unit tests run automatically; E2E/integration tests need user confirmation
6. **NEVER report success without showing actual command output** — "should work" is not verification
## Step 0: Project Discovery (ALWAYS FIRST)
Read `mix.exs` — extract `deps/0`, `aliases/0`, and `cli/0` (for `preferred_envs`). Also check for `.check.exs`. See `${CLAUDE_SKILL_DIR}/references/project-discovery.md` for full patterns.
**Discover tools** (deps): `:credo`, `:dialyxir`, `:sobelow`, `:ex_check`, `:excoveralls`, `:boundary`
… load the full skill through Skill Me