菜单
Run comprehensive Elixir quality checks (format, credo, dialyzer, tests) with proper error handling and reporting. Use when validating code quality, before commits, or preparing for deployment.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | elixir-quality-gate |
| description | Run comprehensive Elixir quality checks (format, credo, dialyzer, tests) with proper error handling and reporting. Use when validating code quality, before commits, or preparing for deployment. |
| allowed-tools | Bash, Read, Grep |
This skill runs comprehensive quality checks on Elixir/Phoenix projects following best practices.
mix format --check-formatted
mix compile --warnings-as-errors
mix credo --strict
mix dialyzer
mix test
Run all checks in sequence:
mix format --check-formatted && \
mix compile --warnings-as-errors && \
mix credo --strict && \
mix dialyzer && \
mix test
If project has a precommit alias:
mix precommit
Run specific checks when iterating:
# Just format
mix format
# Just tests
mix test
# Specific test file
mix test test/my_app/accounts_test.exs
# Just credo
mix credo --strict
Format Failures:
mix format to fix automaticallyCompilation Warnings:
Credo Issues:
Dialyzer Errors:
Test Failures:
mix test test/path/to/test.exs:LINEpriv/plts/ to .gitignore# Run in test environment
MIX_ENV=test mix dialyzer
# Skip dialyzer if building PLT takes too long locally
mix format && mix compile --warnings-as-errors && mix credo --strict && mix test
If using BMAD git hooks, these checks run automatically on:
PLT build fails:
# Clean and rebuild
rm -rf _build priv/plts
mix deps.get
mix dialyzer --plt
Tests fail in CI but pass locally:
MIX_ENV=test mix ecto.createCredo reports too many issues:
BLOCKS shortcuts like modifying dialyzer.ignore or .credo.exs excludes. Enforces fixing actual problems. Use when encountering ANY error, warning, or quality tool complaint.
MANDATORY pre-check before ANY response - ensures you use applicable skills and follow best practices. Use this skill FIRST before responding to any Elixir/Phoenix request.
PROHIBITS placeholder code, default values that mask missing data, and silent failures. Enforces fail-fast with loud errors. Use when implementing ANY function or data structure.
MANDATORY systematic debugging - trace to root cause before proposing fixes. NO random changes, NO symptom fixes, NO "try this". Use when debugging ANY error or issue.
MANDATORY for ANY feature or bugfix - write ExUnit test FIRST, watch it FAIL, then implement. NO exceptions. Use before writing any Elixir production code.
MANDATORY verification before claiming anything works. Run actual commands, read actual output, provide evidence. Use when claiming tests pass, build succeeds, or code works.