airflow
Airflow Operations
Use the Airflow VS Code extension tools for all Airflow interactions. Avoid shell commands for Airflow operations.
Tool Quick Reference
| Tool | Purpose |
|---|---|
list_active_dags |
List active (unpaused) DAGs |
list_paused_dags |
List paused DAGs |
get_running_dags |
Show running or queued DAG runs |
pause_dag |
Pause a DAG |
unpause_dag |
Unpause a DAG |
trigger_dag_run |
Trigger a DAG run |
get_dag_runs |
List DAG runs for a DAG |
get_dag_history |
Daily run history for a DAG |
get_failed_runs |
Failed runs across DAGs |
analyse_dag_latest_run |
Full analysis of latest run (tasks, logs, source) |
get_dag_run_detail |
Full analysis of a specific run |
get_dag_source_code |
Retrieve DAG source code |
go_to_dag_view |
Open DAG view panel |
go_to_dag_log_view |
Open log view panel |
go_to_connections_view |
Open connections panel |
go_to_variables_view |
Open variables panel |
go_to_providers_view |
Open providers panel |
go_to_configs_view |
Open configs panel |
go_to_plugins_view |
Open plugins panel |
go_to_server_health_view |
Open server health panel |
User Intent Patterns
DAG Operations
- "List all DAGs" ->
list_active_dagsandlist_paused_dags - "Show DAG source" ->
get_dag_source_code - "Pause DAG X" ->
pause_dag - "Resume DAG X" ->
unpause_dag
Run Operations
- "Trigger DAG X" ->
trigger_dag_run - "Show recent runs" ->
get_dag_runs - "Why did this fail?" ->
analyse_dag_latest_runorget_dag_run_detail
Logs and Troubleshooting
- "Show logs for task" ->
go_to_dag_log_vieworanalyse_dag_latest_run - "Analyze latest run" ->
analyse_dag_latest_run
System and Config
- "Show connections" ->
go_to_connections_view - "Show variables" ->
go_to_variables_view - "Check server health" ->
go_to_server_health_view
Common Workflows
Investigate a Failed Run
- Find failures:
get_failed_runs - Analyze latest run:
analyse_dag_latest_run - If a specific run ID is known:
get_dag_run_detail - Open logs if needed:
go_to_dag_log_view
Trigger and Monitor
- Trigger:
trigger_dag_run - Check status:
get_dag_runs - Analyze if failed:
analyse_dag_latest_run
Morning Health Check
- Check server health:
go_to_server_health_view - Check running DAGs:
get_running_dags - Review recent failures:
get_failed_runs
More from necatiarslan/airflow-vscode-extension
migrating-airflow-2-to-3
Guide for migrating Apache Airflow 2.x projects to Airflow 3.x. Use when the user mentions Airflow 3 migration, upgrade, compatibility issues, breaking changes, or wants to modernize their Airflow codebase.
29airflow-hitl
Use when the user needs human-in-the-loop workflows in Airflow (approval/reject, form input, or human-driven branching). Covers ApprovalOperator, HITLOperator, HITLBranchOperator, HITLEntryOperator. Requires Airflow 3.1+.
28annotating-task-lineage
Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.
28testing-dags
Complex DAG testing workflows with debugging and fixing cycles. Use for multi-step testing requests like "test this dag and fix it if it fails", "test and debug", "run the pipeline and troubleshoot issues".
27authoring-dags
Workflow and best practices for writing Apache Airflow DAGs. Use when the user wants to create a new DAG, write pipeline code, or asks about DAG patterns and conventions. For testing and debugging DAGs, see the testing-dags skill.
27debugging-dags
Comprehensive DAG failure diagnosis and root cause analysis. Use for complex debugging requests requiring deep investigation like "diagnose and fix the pipeline" or "full root cause analysis".
27