DATA OPS
PR-time schema guard: apply migration to a shadow DB and post a GitHub check
On every pull request touching migration files, spins up a shadow copy of production schema, applies the PR's migrations, diffs the result against staging.
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened touching migrationsGitHub
- ActionProvision shadow DB from prod schemaPostgres
- ActionApply PR migrations to shadow DBPostgres
- LogicDiff shadow schema vs staging; decide pass/fail
- OutputPost GitHub check run with schema deltaGitHub
What it does
When a pull request changes anything under your migrations directory, this workflow replays those migrations against a throwaway shadow database seeded from the current production schema, then diffs the post-migration schema against staging. It posts the computed schema delta as a GitHub check run so reviewers see exactly what the PR will do to the live catalog.
When to use it
Use it to make migration review concrete. Instead of reading SQL and imagining the outcome, reviewers get the actual before/after table, column, and index changes, plus a hard fail if the migration produces drift staging hasn't already validated.
How it works
- 1A GitHub pull-request event with migration-path changes triggers the run.
- 2Provision a shadow Postgres from the production schema snapshot.
- 3Apply the PR's migration files in order to the shadow DB.
- 4Diff the shadow schema against staging's current schema.
- 5Branch: if the delta is empty or matches expectations, mark success; otherwise mark failure.
- 6Post a GitHub check run with the rendered schema delta and status.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.