DATA OPS
dbt Schema-PR PII Pre-Merge Gate
When a GitHub pull request changes a dbt schema, inspects newly added columns for likely PII and posts a blocking review comment listing fields that need a sensitivity tag before…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR opened/updated on dbt schema filesGitHub
- LogicParse diff for newly added column definitions
- ActionClassify each new column for PIIOpenAI
- LogicDrop columns that already have a sensitivity tag
- OutputPost blocking PR review comment with flagged fieldsGitHub
What it does
Triggers on pull requests that touch dbt schema or model files, identifies columns being added in the diff, classifies each for PII, and posts an inline review comment flagging any sensitive column that lacks a `meta.sensitivity` tag so it gets handled before the data ever lands.
When to use it
Use it to shift PII governance left into code review, catching sensitive fields at the PR stage instead of discovering them in the warehouse weeks later.
How it works
- 1A GitHub pull-request webhook fires when schema or model YAML/SQL changes.
- 2Parse the diff to extract newly added column definitions and any existing meta tags.
- 3Classify each new column for PII type and confidence from its name and description.
- 4A filter drops columns that already carry a sensitivity tag.
- 5If any untagged PII remains, post a GitHub review comment listing each field and the suggested tag, marking the check as failing.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 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.