des-code-review

Data engineering pull request review evaluates implemented code, SQL, and pipeline configuration against DES story scope and acceptance criteria to determine merge readiness. It verifies contract compliance, data quality, governance, and CI/CD expectations before approving changes.

When reviewing dbt model changes and SQL transformations, verify transformation logic, data quality expectations, lineage metadata, and contract compliance. Ensure implementation evidence maps to targeted story tasks and architecture design alignment before approving the merge.

To verify CI/CD and data quality guardrails in a pipeline code review, assess orchestration, observability, governance, and security configurations. Confirm safety guardrails are active and documentation is updated before making a merge readiness decision.

Code review for data engineering changes requires providing changed files or diffs alongside relevant DES planning artifacts. You need the story-catalog, dev-task-breakdown, and implementation-plan to map reviewed evidence to story tasks and acceptance criteria.

The best way to structure data engineering code review findings is a decision-ready report classifying issues by severity. This report maps evidence to story tasks and produces a clear merge readiness decision based on lifecycle alignment checks.

You can review notebooks, pipeline configuration, SQL models, and tests in a single code review. The process evaluates all implemented data-engineering changes against the selected DES story scope and lifecycle artifacts to determine overall merge readiness.