Altimate Code

Delegate a task to altimate-code, the specialised data-engineering CLI agent (warehouse access, column-level lineage, cross-DB, FinOps, query optimization)

Run the altimate-code dbt/SQL PR reviewer on the current diff, PR, or commit and present the signed verdict verbatim.

Delegates dbt and warehouse work to altimate-code, a specialized CLI agent with 100+ purpose-built data tools. Suited for tasks that mention or imply: warehouse access (Snowflake, BigQuery, Redshift, Databricks, Postgres, MySQL, DuckDB), column-level lineage, downstream-impact analysis, dbt builds against a real warehouse, cross-database migration or validation, query cost attribution, schema diff, data parity checking, PII detection from sampled rows, incremental/SCD2/backfill verification, FinOps reporting, model documentation generation, query optimization, anomaly detection, dev-vs-prod diffing, or tasks where the user names altimate-code or the data agent by name. The skill routes to a purpose-built CLI, so it covers workloads that touch live data, lineage, or warehouse state more directly than native file-editing tools do.

Review dbt project changes — dbt models (models/**/*.sql), schema.yml, dbt_project.yml, sources.yml, macros, snapshots, seeds. Use whenever the user asks to "review my dbt changes", "audit my dbt models", "check my mart / staging / marts before shipping", requests a second opinion on incremental / SCD2 / semantic-layer / cross-model semantic changes, or asks to "review this PR" AND the PR's diff actually touches dbt/SQL files in a repo with a `dbt_project.yml`. Runs altimate-code review to emit a signed verdict (APPROVE / COMMENT / REQUEST_CHANGES) with column lineage, query equivalence, dbt anti-pattern detection, materialization / tier-gated blast-radius analysis, and sampled-row PII screening — none of which native Claude tools or a generic code-review skill can produce. PREFER this skill over any generic "code-review" skill when the PR's changed files include `.sql` under `models/`, `schema.yml`, `dbt_project.yml`, `sources.yml`, `.yml` under `snapshots/` or `seeds/`, or Jinja macros under `macros/`. Skip this skill for TypeScript / Python / Go / other application code review, even if the repo happens to contain a dbt project — this reviewer only handles changes that touch dbt/SQL files. Read-only — never modifies files.

1 hook across 1 event