菜单
Orchestrates the full Elixir TDD cycle with hard gates and human-in-the-loop approval: write a failing test → confirm fail for the right reason → propose minimal impl → wait for approval → green → refactor → quality gate. Trigger: tdd, red-green-refactor, test first, failing test, write tests before code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
MANDATORY for ALL LiveView work. Invoke before writing LiveView modules or .heex templates. Covers the two-phase rendering lifecycle, mount/handle_event/handle_info/handle_params callbacks, socket assigns, streams, components, form binding, error handling, and PubSub integration. Trigger words: LiveView, live_view, mount, handle_event, handle_info, render, HEEx, socket, assign.
Use when making HTTP requests from Elixir applications. Invoke before integrating external APIs. Covers Req setup, request patterns, error handling, retries, timeouts, and testing with Req.Test. Req is the modern HTTP client for Elixir, replacing HTTPoison and Tesla. Trigger words: Req, HTTP client, HTTP request, API integration, external API, HTTPoison replacement.
MANDATORY for handling large collections in LiveView. Invoke before rendering lists with 100+ items. Covers Phoenix.LiveView.stream/4, stream_insert, stream_delete, DOM patching efficiency, and pagination with streams. Available in LiveView 0.19+. Trigger words: stream, LiveView stream, large list, pagination, DOM patching, stream_insert, stream_delete, phx-update="stream", stream_configure, stream_many, infinite scroll, virtualized list, DOM ID, dom_id.
Safe migration playbook with hard gates and HITL for production risk: plan locks/rollback → implement schema-only migration → migrate/rollback/re-migrate → never mix backfill → expand-contract for NOT NULL → suite green. Trigger: migration, ecto.migrate, add column, index concurrently, expand-contract.
Sequenced PR/diff review workflow with hard gates and optional HITL on Critical fixes: integrity of PR text → load atomic review rules → walk Review Order → severity findings → handoff task list → re-review after Critical changes. Trigger: code review, PR review, review my diff, review before merge, self-review, code audit.
Oban worker playbook with hard gates and HITL: design idempotency and error classes → failing worker test → thin perform/1 (FCIS edge) → retry/discard → failure tests → monitoring. Trigger: Oban, background job, worker, perform, enqueue, unique job.
| name | tdd |
| type | playbook |
| tags | ["playbooks"] |
| license | MIT |
| description | Orchestrates the full Elixir TDD cycle with hard gates and human-in-the-loop approval: write a failing test → confirm fail for the right reason → propose minimal impl → wait for approval → green → refactor → quality gate. Trigger: tdd, red-green-refactor, test first, failing test, write tests before code. |
| metadata | {"version":"1.0.0","user-invocable":"true","entry_point":true,"phases":"Phase 1: Context and RED, Phase 2: HITL approve and GREEN, Phase 3: Refactor, Phase 4: Quality gate","hard_gates":"Test fails for right reason, User approval, Refactor target tests green, Quality gate green","dependencies":{"source":"self","skills":["testing-essentials","elixir-essentials","typespec-dialyzer"]}} |
mix format --check-formatted, mix credo --strict, mix dialyzer, mix test) must pass before opening a PR.Building or changing Elixir behaviour where tests must gate implementation. Prefer pure-core unit tests first (FCIS); use DataCase only when persistence is the behaviour under test.
| Skill | Path | Role |
|---|---|---|
testing-essentials | skills/testing/testing-essentials/ | ExUnit patterns, fixtures |
elixir-essentials | skills/elixir-core/elixir-essentials/ | FCIS language rules |
typespec-dialyzer | skills/elixir-core/typespec-dialyzer/ | @spec on public APIs |
Do not re-teach LiveView/Ecto here — load domain atomics when the feature needs them.
flowchart TD
A[Design minimal test] --> B{Fails for right reason?}
B -->|No| A
B -->|Yes| C[HITL: approve minimal impl]
C --> D[Implement]
D --> E{Target test green?}
E -->|No| D
E -->|Yes| F[Refactor if needed]
F --> G[Quality gate]
G --> H[Done]
mix test path/to/file_test.exsHARD GATE — Test fails for right reason:
UndefinedFunctionError), not syntax/config.If gate fails: Fix the test setup until the failure reason is correct. Do not implement yet.
mix test path/to/file_test.exs — must pass.HARD GATE — User approval:
If gate fails: Re-propose the implementation; do not write unapproved code.
HARD GATE — Refactor target tests green:
If gate fails: Revert the last refactor and take a smaller step.
mix format --check-formatted
mix credo --strict
mix dialyzer
mix test
Add @doc / @spec on new public APIs. Self-review the branch diff (or run code-review playbook) before opening a PR.
HARD GATE — Quality gate green:
mix format --check-formatted, mix credo --strict, mix dialyzer, and mix test all exit 0.@doc and @spec.If gate fails: Fix formatting, Credo, Dialyzer, or test failures before opening a PR.
| Problem | Action |
|---|---|
| Wrong-reason fail | Fix test/config; stay in Phase 1 |
| Impl still red | Diagnose; re-propose if approach changes (HITL again) |
| Refactor turns red | Revert last step; smaller extraction |
| Quality red | Fix before PR; do not skip gates |
## TDD Report
**Feature:** <behaviour under test>
**Test file:** `path/to/file_test.exs`
**HARD-GATE results:**
- Test fails for right reason: PASS / FAIL
- User approval: PASS / FAIL
- Quality gate green: PASS / FAIL
**Commands run:**
| Command | Exit | Notes |
|---------|------|-------|
| `mix test path/to/file_test.exs` (RED) | non-zero / unexpected | |
| `mix test path/to/file_test.exs` (GREEN) | 0 / non-zero | |
| `mix format --check-formatted` | 0 / non-zero | |
| `mix credo --strict` | 0 / non-zero | |
| `mix dialyzer` | 0 / non-zero | |
| `mix test` | 0 / non-zero | |
**Refactor steps:** <list>
**Public API docs/specs:** <list>
**Verdict:** APPROVE / REQUEST_CHANGES