From ad-migration
Use when editing, generating, reviewing, or debugging migrated dbt unit test specs and review artifacts that must stay consistent across paired test skills.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ad-migration:test-invariantsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Shared contract for `generating-tests` and `reviewing-tests`. Keep these rules stable so the pair can evolve without drifting.
Shared contract for generating-tests and reviewing-tests. Keep these rules stable so the pair can evolve without drifting.
Do not use this skill for command orchestration, readiness checks, or fixture-quality heuristics that belong only to review.
| Invariant | Rule |
|---|---|
| Source of truth | Re-derive branches from current SQL; stored manifests may be stale |
| Artifact ownership | Generator owns TestSpec; reviewer owns TestReviewOutput |
| Cross-artifact IDs | Branch, scenario, uncovered, and feedback IDs must resolve within the owning artifact |
| Repair scope | On reviewer-driven reruns, repair named gaps first and preserve non-targeted approved scenarios and expect blocks |
| Evidence standard | Coverage and verdict claims must be derivable from artifact content, not prose |
branch_manifest as authoritative.npx claudepluginhub accelerate-data/vibedata-official --plugin ad-migrationCreates YAML unit tests for dbt models that mock inputs and validate outputs. Use for complex SQL logic, edge cases, bug fixes, or TDD.
Generates SQL validation notebooks for dbt PR changes with before/after comparison queries. Useful for data teams validating model changes before deployment.
Audits existing test suite alignment after code changes, identifying stale assertions, tests for deleted code paths, and coincidence tests. Use after any code modification.