DATA OPS
Schema Contract Check on dbt PRs via GitHub
Runs on every pull request that touches dbt models, parses the changed model schemas.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR opened/updated touching models/GitHub
- ActionFetch changed + base-branch schema filesGitHub
- LogicDiff columns; flag removals, retypes, new NOT NULL on contracted models
- ActionPost inline review comment on violationsGitHub
- OutputSet pass/fail commit status to gate mergeGitHub
What it does
Gates schema changes at the pull-request stage instead of in production. When a PR modifies dbt model or schema YAML, it extracts the proposed columns, compares them to the committed contract for any model marked as contracted, and fails a GitHub status check if the change would break a downstream consumer.
When to use it
When your warehouse models are version-controlled in dbt and you want schema discipline enforced in code review — catching a dropped or renamed column before it ever merges, rather than alerting after it ships.
How it works
- 1A GitHub pull_request event triggers the run when files under the models path change.
- 2Fetch the changed files and the base-branch versions via the GitHub API.
- 3Parse columns from both the proposed and base schema definitions.
- 4Logic step flags removed columns, type changes, and added-NOT-NULL on any model whose meta marks it contracted.
- 5Post an inline review comment on the offending YAML lines.
- 6Set a GitHub commit status (pass or fail) so merge is blocked on violations.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
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.
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.
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 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…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
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.