Adversarial Elixir Gate

An Elixir/OTP/Ecto/Phoenix review gate — pass/fail: a single blind reviewer subagent judges the work against this gate's rules with an adversarial mandate, and the work passes only when every rule is PASS or N/A. This skill renders verdicts; it never fixes the work.

The rules target one failure mode: code that imported the wrong mental model onto the BEAM — OO/enterprise layering, processes treated as objects, anemic data, defensive control flow, transliterated loops, and needless metaprogramming. They are grounded in the official Elixir anti-pattern catalogs and each carries an Evidence of violation paragraph so a reviewer can decide PASS/FAIL/N/A from artifact evidence alone. Judgment-call refactor guidance stays in the advisory sibling staff-level-elixir.

When to Apply

• An Elixir diff, feature, or PR is about to merge and needs an objective PASS/FAIL, not advisory feedback.
• An agent (Claude, Codex) authored the code and you want an independent check that it did not reproduce OO habits — repository wrappers over Ecto, *Service/*Manager tiers, a GenServer per entity, DI behaviours for a single implementation, raise/rescue as an if.
• Code ported from Java/Ruby/Python (or written by developers newer to the BEAM) needs auditing for paradigm fit before it calcifies.
• A refactor claims to have "made it idiomatic" and you want the claim verified, not assumed.

Do not apply to non-Elixir codebases (the reviewer prompt's precondition aborts with "GATE NOT APPLICABLE"), or when the user wants explanations and refactors rather than a verdict — that is staff-level-elixir's job. arch-delete-repository-over-ecto goes N/A when the target has no Ecto; flow-normalize-at-boundary goes N/A when the target has no external-input path. Remedies newer than the project's Elixir version are judged against the nearest available remedy — the reviewer prompt carries the version-gate table.

Review Protocol

Follow these steps exactly — the gate's value is that every review runs the same way.

1. Identify the target. Pin down exactly what is under review (a diff, a set of files, a PR) and note the ref/paths so the review runs against an unambiguous, fixed target. Record the Elixir version and key deps (from mix.exs — the elixir: requirement, Phoenix/Ecto presence). Include the repo root in the target description — arch-drop-di-behaviour-single-impl, type-protocol-over-type-dispatch, proc-consolidate-interface, and meta-use-is-not-import require searching beyond the diff for implementing modules, duplicate dispatch sites, callback owners, and __using__ bodies.
2. Load the rules. Read references/_sections.md and every rule file in references/ (all arch-*.md, proc-*.md, type-*.md, flow-*.md, iter-*.md, meta-*.md files).
3. Compose the reviewer prompt. Fill references/reviewer-prompt.md with the rules, the target, and the stack facts. The composed prompt must be fully self-contained — a reviewer sees no conversation history, so nothing may refer to context outside the prompt.
4. Dispatch one blind reviewer. Launch a single Task subagent whose entire input is the composed prompt — no conversation context, no commentary alongside it.
5. Render fail-closed. The reviewer's structured output is the verdict — there is no merge step. Overall verdict is PASS only when every rule is PASS or N/A; any single FAIL fails the gate. Never average, weigh severity, or waive a rule — a "minor" FAIL is a FAIL. If the reviewer returns "GATE NOT APPLICABLE" (not an Elixir target), stop and report that instead of a verdict.
6. Render the verdict. Fill assets/templates/verdict.md. On FAIL, aggregate the reviewer's "missing for PASS" suggestions into the fix list, each with its location, ordered by category importance. Every rule whose final result is FAIL must appear in the fix list with a change concrete enough to apply as written — if the reviewer's suggestion only restates the violation, derive the fix from the rule's Correct example before rendering.

If the same rule flips verdicts across re-reviews of an unchanged target, or a human reads the evidence and overrides the verdict, that is a decidability bug in the rule — record it in gotchas.md and sharpen the rule; do not override the gate.

Verdict Format

The reviewer returns, per rule: PASS | FAIL | N/A, evidence (file:line or a quote — required for PASS as well as FAIL), and for every FAIL, the fix that flips the rule to PASS once applied — the named change plus its location, never a restatement of the violation. The final report follows assets/templates/verdict.md.

Rule Categories

Gotchas

Read gotchas.md before dispatching reviewers — it pre-records scope guards (style lore reviewers try to import, the two name-the-replacement rules, the numeric god-struct line) so reviewers do not judge outside the rules.

Related Skills

• staff-level-elixir — the advisory sibling: greenfield "which tool, which convention" guidance and the judgment calls this gate deliberately excludes. Use it to write or fix code; use this gate to verdict it.
• elixir-meta-programming — how to build macros/DSLs correctly once one is genuinely warranted (the complement to this gate's meta- rules).
• adversarial-swift / adversarial-rust / adversarial-zod / adversarial-ts-patterns / adversarial-tanstack — sibling gates for other stacks; same protocol, different rules.

Reference Files