What problem does it solve?
Deploying broken or non-compliant Airflow DAGs causes pipeline failures, import errors, and unplanned downtime, requiring hours of manual debugging to resolve issues that could have been caught earlier in the development cycle.
Core Features & Use Cases
- Static DAG Validation: Scans Airflow DAG files for syntax errors, missing imports, and structural issues like orphaned tasks or missing schedule intervals.
- Project Convention Enforcement: Checks for compliance with team standards, including correct path resolution for Airflow job and config paths, and proper Unity Catalog write patterns for Bronze data runners.
- Use Case: Data engineering teams can integrate this validation into their CI/CD pipeline to automatically reject DAGs with critical issues before they are deployed to production, preventing failed pipeline runs and data delivery delays.
Quick Start
Use the validate-dag skill to check your Airflow DAG file at path 'dags/my_daily_etl_dag.py' for errors and compliance with project standards.