dbt-preflight skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
dbt-preflight is agent-read markdown (skill) from yeaight7/agent-powerups: Use when a dbt change needs preflight before a PR, review, or merge -- changed models, snapshots, seeds, macros, or semantic YAML whose blast radius and test coverage are not yet known..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## Purpose Inspect a dbt change set before it ships: identify which assets changed, estimate downstream impact, detect likely gaps in testing, contracts, documentation, and YAML alignment, and recommend the narrowest safe validation path. Preflight is read-only — do not edit code unless explicitly asked. ## When to Use - Before opening a PR in an analytics repository - Reviewing someone else's dbt change - Assessing the risk of a change whose downstream impact is unclear ## Inputs - The change set (branch diff or working tree) - The dbt project, for lineage and selector queries ## Workflow 1. **Enumerate changed assets:** ```bash git diff --name-status origin/main...HEAD ``` Classify each change: models, snapshots, seeds, macros, tests, schema YAML, semantic models, metrics, saved queries, exposures or BI-facing assets. 2. **Estimate blast radius.** For each changed model, list downstream dependents: ```bash dbt ls --select <model>+ ``` If a production manifest is available, cover the whole change set at once: ```bash dbt ls --select state:modified+ --state <path-to-prod-artifacts> ``` 3. **Run the review checklist.** Check for: …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/dbt-preflight@git:20260605.0e1a602mdr add yeaight7/agent-powerups/dbt-preflight@sha256:33c8b7442f79a7a6Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_vomwckt27t44nzwe)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260605.0e1a602 latest | 2026-06-05 | 0e1a602 | 3,204 B | A | view · diff |
| git:20260502.75ae8f1 | 2026-05-02 | 75ae8f1 | 1,787 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3204 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vomwckt27t44nzwe GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/dbt-preflight GET https://markdownregistry.com/api/v1/blob/33c8b7442f79a7a6f0cfc08d867850aebbc5e215a8e4526ab08a09f2490f617d
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups