odin-testing

Plugin odin-testing from marketplace odin-marketplace in OutlineDriven/odin-claude-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (25)

• behavior-validator

  Use when asked to validate a web app, CLI, API, or generated artifact against a source-blind behavior contract. Not for source or remote-system changes.

• browser-qa

  Use when the user runs /browser-qa for report-only QA results without entering a fix loop. Not for remote, credential, publish, deploy, or irreversible changes.

• control-cli

  Use when asked to reproduce, profile, or verify CLI/TUI behavior. Produces a deterministic transcript or profile proof with session cleanup. Not for CLI design advice, use cli-for-agents.

• control-ui

  Use when asked to verify or reproduce browser or Electron UI behavior with before-and-after evidence and no leftover processes. Not for remote, credential, publish, deploy, or irreversible changes.

• evaluation-leakage-audit

  Use when reviewing an evaluation, benchmark, or scoring harness for leakage, or a validation result that looks self-confirming. Modes: leakage, self-audit. Not for one claim: use verify-both-ways.

• exhaustive

  Use when asked to prove coverage, find missing cases, or enumerate state, decision, requirement, or behavior space. Not for round-based or single-property tests: use askme, property-test-authoring.

• full-product-evaluation

  Use when a complete product needs production-like acceptance evidence against documented acceptance criteria. Not for single-component evaluation or evaluation without documented criteria.

• lighter-checks

  Use when verification is looping, would re-run untouched code, or duplicates an established proof. Not for tasks that require source or remote-system changes.

• meaningful-test-coverage

  Use when a test surface needs behavior-guarding coverage raised to a configured target with mutation kill evidence. Not for line-coverage inflation without mutation proof.

• mutation-campaign-configuration

  Use when asked to initialize, scope, estimate, configure, validate, or optimize a mewt, muton, or mutation testing campaign before execution. Writes the TOML config. Not for running it: use the mewt CLI.

• mutation-triage-genotoxic

  Use when a mutation campaign leaves surviving mutants needing triage. Classifies each as false-positive, missing-test, genotoxic, or removable. Not for setup: use mutation-campaign-configuration.

• possible-worlds-qa

  Use when a product surface must be tested against extreme or hostile worlds. Not for design disputes: use possible-worlds. Not for remote, credential, publish, deploy, or irreversible changes.

• proof-driven

  Use when property-based testing, theorem proving, or formal proof tactics require zero unproven properties. Not for remote, credential, publish, deploy, or irreversible changes.

• property-test-authoring

  Use when authoring property tests, assessing PBT fit for a code path, reviewing existing property tests, or triaging a failing counterexample. Not for test-first features: use tdd.

• reproduce-bug-report

  Use when a bug report or UI-visible defect exists. Reproduces it locally. Not for fixing the bug: use reproduce-and-fix-issues.

• run-smoke-tests

  Use when asked to run smoke tests or verify a local build, applying only minimal unblocking fixes. Not for iterative bug fixing: use reproduce-and-fix-issues.

• strict-validation-setup

  Use when a user invokes a strict-mode validation or verifiable-goals loop setup. Not for remote, credential, publish, deploy, or irreversible changes.

• tdd

  Use when developing a fix or feature test-first, plan a TDD build, or work red-to-green in slices. Not for hardening: use tests-adversarial. Not for deleting weak tests: use tests-purge-unneeded.

• test-migration-coverage-gate

  Use when about to delete a test that a new harness, suite, or scenario covers. Not for tests that catch no real bug: use tests-purge-unneeded. Not for untracked data or changes without VCS rollback.

• test-suite-acceleration

  Use when a test suite is too slow and needs acceleration without weakening behavior or coverage, or CI parallelization must fix serial execution. Not for deleting tests: use tests-purge-unneeded.

• tests-adversarial

  Use when hardening error handling, validating boundary behavior, or hunting silent failures. Not for feature development: use tdd. Not for test deletion: use tests-purge-unneeded.

• tests-purge-unneeded

  Use when a legacy, slow, or duplicate test suite needs purging, a post-refactor sweep is due, or types cover a contract. Not for tests a new harness supersedes: use test-migration-coverage-gate.

• validation-first-driven

  Use when protocols, workflows, concurrency, or lifecycle state need states, transitions, and temporal properties. Not for domain models: use type-driven. Not for contracts: use contract-driven.

• verification-skill

  Use when asked to create a project-local executable verification skill, or repair one whose commands, paths, or assertions drifted. Not for remote or deployed verification.

• verify-this

  Use when a measurable claim needs before/after proof. Not for fact-checking or done-claim gating: use verify-both-ways or verification-before-completion.

Similar plugins