skills.rest
accelerate-data
accelerate-dataOFFICIAL
Explore all skills by this author →
WebsiteGitHub

test-invariants

Enforce stable invariants across test-generation and test-review workflows for migrated dbt unit tests.

3|Updated Feb 27, 2026
Search Tags:#consistency#dbt#governance#artifacts#test#invariants#pairing
One-click install
npx skills add https://github.com/accelerate-data/migration-utility --skill test-invariants
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-invariants
Source: https://github.com/accelerate-data/migration-utility/tree/main/skills/test-invariants
Command: npx skills add https://github.com/accelerate-data/migration-utility --skill test-invariants

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures stable, cross-skill invariants for test specifications and review artifacts in migrated dbt workflows, preventing drift between paired test skills.

Core Features & Use Cases

  • Maintain a single source of truth for TestSpec and TestReviewOutput ownership across generating-tests and reviewing-tests.
  • Detect and repair inconsistencies in branch, scenario, and feedback IDs to keep artifacts aligned.
  • Provide a lightweight contract that can be referenced during test development and reviews.

Quick Start

Review and align test specifications between the generating-tests and reviewing-tests skills to ensure consistent TestSpec and TestReviewOutput artifacts.

Frequently Asked Questions about test-invariants

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep dbt unit test invariants stable across paired skills?▼

To keep dbt unit test invariants stable, align TestSpec and TestReviewOutput artifacts during test generation, review, and repair passes. This enforces consistent branch, scenario, and feedback IDs to prevent drift between paired test workflows.

What is the best way to resolve cross-artifact ID inconsistencies in dbt test specs?▼

Resolving cross-artifact ID inconsistencies involves detecting and repairing mismatched branch, scenario, and feedback IDs between TestSpec and TestReviewOutput. This formalizes ownership and repair scope to keep test artifacts aligned and traceable.

Why does test specification drift occur when migrating dbt unit tests?▼

Test specification drift occurs when paired test-generation and test-review workflows lack a single source of truth for TestSpec and TestReviewOutput ownership. Without enforced invariants, branch and scenario IDs become misaligned across editing passes.

Can I use this invariant contract during dbt test editing and repair passes?▼

Yes, you can reference this lightweight invariant contract during dbt test editing, generation, review, and repair passes. It ensures consistent TestSpec and TestReviewOutput artifacts by formalizing ownership and cross-artifact ID resolution.

Does test-invariants work without additional dbt dependencies?▼

Yes, test-invariants operates without additional dependencies. It provides a standalone contract to align TestSpec and TestReviewOutput ownership across paired test skills, ensuring consistency and traceability in migrated dbt workflows.

Related Skills

Explore More Data & Analytics Skills→
winhokwinhok
5

testspec-shared

Consolidate shared TestSpec conventions, contracts, and templates for cross-skill workflows.

Community
Basic
ThalesGroupThalesGroup
19

agilab-testing

Execute targeted AGILAB tests across unit, smoke, and regression suites.

Official
Advanced
sperictaosperictao
1

trellis-check

Automate code quality checks for specs, lint, types, tests, and data flow.

Community
Intermediate
ArvorCoArvorCo
96

analyze

Validate cross-artifact consistency across spec, plan, tasks, and checklist.

Community
Basic