dbt-pr-review

Reviews dbt pull requests with deterministic lineage, equivalence, and PII checks.

803|134|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/AltimateAI/altimate-code --skill dbt-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbt-pr-review
Source: https://github.com/AltimateAI/altimate-code/tree/main/.opencode/skills/dbt-pr-review
Command: npx skills add https://github.com/AltimateAI/altimate-code --skill dbt-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing dbt pull requests by reading diffs alone misses downstream breakage, semantic changes, and PII exposure. This Skill produces a signed APPROVE, COMMENT, or REQUEST_CHANGES verdict where every blocking finding is backed by a deterministic engine call rather than guesswork.

Core Features & Use Cases

  • Deterministic verdict engine: Runs dbt_pr_review against the working tree or an explicit base/head range, returning a signed envelope with a risk tier and findings grouped by severity.
  • Evidence-backed findings: Each blocking finding carries proof such as column-lineage blast radius, query equivalence counterexamples, PII classification, or contract violations.
  • Configurable rubric: A per-repo .altimate/review.yml controls mode (comment vs gate), severity thresholds, dialect, reviewer lanes, and blocking categories.
  • Use Case: Before merging a dbt model refactor, run the review to confirm the rewrite is query-equivalent, check which downstream models consume changed columns, and catch PII exposure — all in one verdict.

Quick Start

Ask the agent to review my dbt pull request against origin/main and give me the verdict with any blocking findings.

Frequently Asked Questions about dbt-pr-review

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

FAQPage Schema
How do I review a dbt pull request before merging?

Run the dbt_pr_review tool with no arguments to review the working tree against origin/main, or pass explicit base and head refs for a PR range. It returns a signed verdict envelope with findings grouped by severity.

How do I check if a dbt refactor preserves query results?

The review runs a query equivalence check that proves whether a rewrite returns identical results. An UNDECIDABLE result is reported as a warning, never a block, with a recommendation to run a data-diff instead.

Can dbt PR review block merges automatically?

Yes, set mode to gate in .altimate/review.yml so REQUEST_CHANGES verdicts block the merge. The default comment mode posts findings without blocking, which is recommended until you trust the false-positive rate.

What happens when there is no dbt manifest or warehouse connection?

The review runs in degraded mode as a lint-only check. Lineage, equivalence, and data-impact are not verified, and the output explicitly states that these checks were skipped.

What findings block a dbt pull request by default?

By default, REQUEST_CHANGES triggers on critical findings in blocking categories: broken lineage with downstream consumers, contract violations, PII exposure, or proven non-equivalent rewrites, plus three or more warnings.