← ClaudeAtlas

data-quality-gatelisted

Use when a data pipeline needs one CI step that fails the build when data quality drops. Gathers check results from dbt, Great Expectations or Soda, applies severity-aware thresholds and returns a single go/no-go decision with a reason per check.
testland/qa-skills · ★ 0 · Data & Documents · score 72
Install: claude install-skill testland/qa-skills
# data-quality-gate ## Overview The three engines (`dbt-testing`, `great-expectations`, `soda-checks`) each produce their own per-check output: dbt writes `run_results.json` ([dbt-run-results][1]), Great Expectations returns a JSON result with a `success` flag and a `results` list ([gx-run-validation-definition][2]), and Soda emits a per-check pass/fail summary in stdout (and to Soda Cloud) ([sodacl-overview][3]). [1]: https://docs.getdbt.com/reference/artifacts/run-results-json [2]: https://docs.greatexpectations.io/docs/core/run_validations/run_a_validation_definition [3]: https://docs.soda.io/soda-v3/soda-cl-overview.md This skill builds a **single release-readiness gate** that consumes those heterogeneous outputs, applies severity-aware thresholds, and emits one `go` / `no-go` decision the CI pipeline can act on. The skill is deliberately engine-agnostic at the surface so a project can mix engines (e.g. dbt for transformation tests + GX for ingestion validation + Soda for cross-team observability) and still ship a single gate. ## When to use - A pipeline runs more than one data-quality engine and needs a unified pass/fail summary (instead of one CI job per engine). - Some checks are blocking (`severity: error`) and others should warn but not stop the pipeline (`severity: warn`) - the gate must distinguish. - The team wants a structured artifact (JSON / markdown table) for PR comments, dashboards, or post-mortems - not just `exit 1`. - A migration is rolling