phxverify

# 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` **Discover test commands** (aliases + deps): - Unit: `mix test` (always), or custom alias like `mix test.with_coverage` - E2E: `mix playwright.test`, `mix cypress.run`, or similar (check `preferred_envs` for `MIX_ENV`) - Fast E2E: `mix playwright.run` (skips setup — for re-runs) **Discover composite runner**: If `.check.exs` exists, read it — `mix check` may handle compile, format, credo,...