verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
npx skills add oliver-kriska/claude-elixir-phoenix --skill verify --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Iron Laws
- Step 0: Project Discovery (ALWAYS FIRST)
- Verification Sequence
- Step 1: Compile
- Step 2: Format
- Step 3: Credo
- Step 4: Test
- Step 5: Dialyzer
- Step 6: Sobelow
- Step 7: Additional Test Offer
- Quick Reference
- Usage
What does the verify skill do?
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
How do I install it?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill verify --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From oliver-kriska/claude-elixir-phoenix, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.