DATA OPS
Pre-Merge dbt Contract Drift Gate on Pull Request
On every pull request that touches a dbt model, checks the proposed contract against the live Snowflake table and posts a pass/fail review comment so contract changes never merge…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request touches dbt model filesGitHub
- ActionRead proposed contract from PR branchGitHub
- ActionQuery Snowflake for live table shapeSnowflake
- LogicDiff proposed contract vs. live warehouse columns
- OutputPost pass/fail review comment on the PRGitHub
What it does
This workflow turns contract drift into a code-review gate instead of a runtime surprise. When a pull request edits a dbt model file, it reads the proposed contract from the PR branch and compares it to the actual Snowflake table the model selects from. If the contract claims a column or type the warehouse does not have, it posts a failing review comment listing the discrepancies; if everything lines up, it posts an approving check.
When to use it
Use it when analysts edit dbt contracts in pull requests and you want CI to confirm the contract matches reality before merge. It stops the common failure where someone updates a contract for a column the upstream team has not actually shipped yet.
How it works
- 1A GitHub pull-request event fires on changes under the models path.
- 2Read the proposed contract definitions from the PR head.
- 3Query Snowflake for the live shape of each referenced table.
- 4Diff proposed contract vs. live warehouse columns and types.
- 5Branch on whether discrepancies exist.
- 6Post a pass or fail review comment on the PR with the exact mismatches.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.