메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | background-job |
| type | playbook |
| tags | ["playbooks"] |
| license | MIT |
| description | 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. |
| metadata | {"version":"1.0.0","user-invocable":"true","entry_point":true,"phases":"Phase 1: Design, Phase 2: RED, Phase 3: HITL impl, Phase 4: Failure paths, Phase 5: Monitor","hard_gates":"Idempotency and error classification, Failing worker test, Thin perform/1, Failure paths tested, User approval and green suite","dependencies":{"source":"self","skills":["oban-essentials","testing-essentials","elixir-essentials","telemetry-essentials"]}} |
perform/1 is written.perform/1 is a thin edge: fetch IDs → pure core → return tagged tuple.mix format --check-formatted, mix credo --strict, and the full mix test suite are green before the PR is opened.Adding or hardening Oban (or similar) background workers.
| Skill | Path | Role |
|---|---|---|
oban-essentials | skills/infrastructure/oban-essentials/ | Worker patterns |
testing-essentials | skills/testing/testing-essentials/ | Oban.Testing |
elixir-essentials | skills/elixir-core/elixir-essentials/ | FCIS |
telemetry-essentials | skills/performance/telemetry-essentials/ | Metrics |
flowchart TD
A[Idempotency + error classes] --> B[Failing perform test]
B --> C[HITL: approve worker design]
C --> D[Thin perform/1 + context]
D --> E[Retry discard unique tests]
E --> F[Telemetry optional]
Document: queue, args (IDs only), idempotency key, transient vs permanent errors.
HARD GATE — Idempotency and error classification:
If gate fails: Revisit the design doc; do not write perform/1 until the contract is clear.
Worker test expecting success/cancel/error paths; must fail until implemented.
HARD GATE — Failing worker test:
perform/1 is written.If gate fails: Adjust the test so it exercises missing behaviour, not a syntax/config mistake.
perform/1 as edge: fetch → domain → tuple.HARD GATE — Thin perform/1:
perform/1 fetches IDs, delegates to a pure core/domain function, and returns a tagged tuple.If gate fails: Extract logic into a context or pure function; re-HITL the design.
Cover: not found → cancel; transient → error/retry; duplicate → unique.
HARD GATE — Failure paths tested:
not_found path returns {:cancel, _} or equivalent.unique options or idempotency key.If gate fails: Add missing tests and handling for each failure class.
Attach telemetry/logging for failures if production-bound.
HARD GATE — User approval and green suite:
mix format --check-formatted, mix credo --strict, and mix test pass.If gate fails: Fix formatting, Credo, or test failures; re-HITL if the design changed.
Non-idempotent side effects → add guards/unique; re-test double perform.
## Background Job Report
**Design:** <queue, args, idempotency key, error classes>
**Test command:** `<mix test command>`
**HARD-GATE results:**
- Idempotency and error classification: PASS / FAIL
- Failing worker test: PASS / FAIL
- Thin perform/1: PASS / FAIL
- Failure paths tested: PASS / FAIL
- User approval and green suite: PASS / FAIL
**Verdict:** APPROVE / REQUEST_CHANGES
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.
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.
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.