table-driven-tests
Review that tests covering multiple scenarios use table-driven style instead of inline sequential blocks.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Review that tests covering multiple scenarios use table-driven style instead of inline sequential blocks.
Review that code and events use terminology whose semantics match the operation (e.g., not Preempted for migration).
Flag extra checks that are logically unreachable at the call site — they add noise and can mask future regressions.
Review that newly exported functions have callers outside the package, lowercasing those that don't.
Flag per-reconcile-cycle log lines emitted at V(2) — recurring reconcile-loop logs must be V(4) or higher.
Use the @executor-js/emulate service emulators (GitHub, Google, Stripe, Resend, WorkOS, …) to test integrations for real — full OpenAPI specs, working OAuth flows, mintable credentials, and a request ledger for assertions. Use when a test or demo needs a real-shaped upstream API, an OAuth/OIDC provider, a spec to feed addSpec, or proof that a request actually landed.
Keep tests deterministic and Effect-aware. Use when lint flags direct vitest imports or conditional assertions inside tests.
Use when reviewing, writing, or committing changes that touch model/config.go or any TOML config struct in this repo. Verifies that every added, renamed, or removed TOML field has a matching update in sesh.schema.json so the JSON schema used by TOML editors (via `#:schema` directive) stays in sync with the Go config model. Trigger whenever a diff touches files under model/, configurator/, or any struct tagged with `toml:"..."`.
How to integrate, update, and configure the dart_skills_lint validation tool within a repository. Make sure to use this skill whenever the user asks to update dart_skills_lint, configure skills validation tests, fix skills linter dependency drifts, verify repository state before editing, optimize lint rules execution, or draft pull request submission commands.