一键导入
dbt-ci
// Use when generating GitHub Actions workflows for dbt, adding dbt build/test/docs steps, or configuring state-based selection with --select state:modified+. Provides templates for both full builds (CD) and incremental builds (CI).
// Use when generating GitHub Actions workflows for dbt, adding dbt build/test/docs steps, or configuring state-based selection with --select state:modified+. Provides templates for both full builds (CD) and incremental builds (CI).
| name | dbt-ci |
| description | Use when generating GitHub Actions workflows for dbt, adding dbt build/test/docs steps, or configuring state-based selection with --select state:modified+. Provides templates for both full builds (CD) and incremental builds (CI). |
Use for production baseline workflows where you build everything:
If uv:
- name: Run dbt
run: |
uv run dbt deps
uv run dbt build --target {TARGET}
uv run dbt docs generate --target {TARGET}
If pip:
- name: Run dbt
run: |
source .venv/bin/activate
dbt deps
dbt build --target {TARGET}
dbt docs generate --target {TARGET}
Use --state for state-based selection when comparing against a baseline:
If uv:
- name: Run dbt (modified models only)
run: |
uv run dbt deps
uv run dbt build --target {TARGET} --select state:modified+ --state {STATE_PATH}
uv run dbt docs generate --target {TARGET} --select state:modified+ --state {STATE_PATH}
If pip:
- name: Run dbt (modified models only)
run: |
source .venv/bin/activate
dbt deps
dbt build --target {TARGET} --select state:modified+ --state {STATE_PATH}
dbt docs generate --target {TARGET} --select state:modified+ --state {STATE_PATH}
| Variable | Description | Example |
|---|---|---|
{TARGET} | dbt target/profile name | prod, ci, dev |
{STATE_PATH} | Path to baseline manifest for comparison | target-base |
state:modified - Only models with code changesstate:modified+ - Modified models + downstream dependencies+state:modified+ - Upstream + modified + downstreamRequires --state <path> pointing to a directory with baseline manifest.json.
state:modified+ in CI to only rebuild what changeddbt docs generate to create artifacts for comparison tools--target to your profiles.yml environment (prod, ci, dev)--state flagpython-uv-ci skill for Python/uv environment setup stepspython-pip-ci skill for Python/pip environment setup stepsrecce-cloud-ci skill for Recce Cloud upload/download stepsLightweight pre-commit verification for dbt model changes in the single-environment dev loop — when the user has a warehouse-connected dbt project but no `target-base/` artifacts. Triggers when: user asks to verify a model change, check whether an edit is safe to commit, sanity-check a filter/aggregation/join change without setting up a base environment, or asks for a quick risk read before running /recce-review. Uses Tier-1 evidence only — column lineage, AST analysis, and targeted current-env SQL probes. Routes to /recce-review when `target-base/` is fresh.
Automatically provide Recce guidance in dbt projects. Triggers when: working in dbt project directory, discussing PRs or data changes, after dbt command execution, or when user asks about data validation.
Review dbt model data changes using Recce. Triggers when: user asks to review data changes, check data impact, run recce review, validate model changes before committing, review a Recce Cloud PR session, connect MCP to a cloud session, pastes a GitHub PR / GitLab MR URL, or pastes a Recce Cloud session/launch URL for cloud-mode review.
Use when the user asks to "run eval", "recce eval", "evaluate plugin", "benchmark recce", "compare with plugin", "compare without plugin", "eval case", "score eval", "eval report", "eval history", "list eval scenarios", "list eval cases", "show eval history", "run eval case", or wants to measure the Recce Review Agent's effectiveness compared to pure Claude Code without the plugin.
Use when the user asks to "validate MCP", "run MCP E2E", "run E2E validation", "benchmark MCP performance", "test the plugin flow", "test MCP integration", "compare MCP versions", "show benchmark history", "驗證 MCP", "跑 E2E", "看歷史紀錄", or wants to verify the recce plugin's full event chain works end-to-end and measure agent performance metrics.
This skill should be used when the user asks to "update readme", "review readme", "refresh readme", "audit readme", "fix the main readme", "改 readme", "檢查 readme", or when the root README.md needs to reflect new plugin changes, version bumps, or feature additions.