reviewing-tests

Review dbt test specs for branch-coverage gaps and fixture-quality issues.

3|Updated Feb 27, 2026

Search Tags:#quality #dbt #review #fixtures #code-review #branch-coverage #test-specs

Ready to run

npx skills add https://github.com/accelerate-data/migration-utility --skill reviewing-tests-accelerate-data

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewing-tests
Source: https://github.com/accelerate-data/migration-utility/tree/main/skills/reviewing-tests
Command: npx skills add https://github.com/accelerate-data/migration-utility --skill reviewing-tests-accelerate-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generating test specs for dbt can produce branch-coverage gaps, fixture-quality problems, and unresolved warnings. This Skill provides a quality gate to review and validate those tests before integration, ensuring independent review and consistent artifact quality.

Core Features & Use Cases

Independently review generated test specs per object to isolate issues.
Validate fixture realism, FK consistency, and edge-case coverage across tables and views.
Output a standards-aligned review manifest and actionable feedback for generators.

Quick Start

Review the generated test specs on a branch-by-branch basis and produce a conclusive verdict.

Frequently Asked Questions about reviewing-tests

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

FAQPage Schema

How do I review generated dbt test specs for branch-coverage gaps?▼

Review generated dbt test specs by validating branch coverage on a branch-by-branch basis to surface edge-case gaps. This process isolates coverage issues per object, producing reviewer-centric metrics and actionable feedback for the test generators.

What is fixture quality validation in dbt code review?▼

Fixture quality validation in dbt code review is the process of checking test fixtures for realism and foreign key consistency across tables and views. It ensures generated test data accurately represents edge cases before integration.

How do I validate edge-case coverage across dbt tables and views?▼

Validate edge-case coverage across dbt tables and views by independently reviewing generated test specs per object. This isolates missing edge cases and fixture-quality issues, producing a standards-aligned review manifest for corrective feedback.

Can I use a quality gate to review dbt tests before integration?▼

Yes, you can use a quality gate to review dbt tests before integration. It independently validates generated test specs, resolving branch-coverage gaps and fixture-quality problems to ensure consistent artifact quality and produce a conclusive verdict.

What are the limitations of automated dbt test generation?▼

Automated dbt test generation can produce branch-coverage gaps, fixture-quality problems, and unresolved warnings. It requires an independent review process to validate edge cases and ensure the generated test artifacts meet integration standards.