Skip to content
Skills Library
Data & analytics · Analysis

debugging-dags

/debugging-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".

Licence
Apache-2.0
Last repository change
02.06.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.06.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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".

Triggers from the description

diagnose and fix the pipelinefull root cause analysis
Original author description

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".

How it works

  1. Step 1: Identify the Failure
  2. Step 2: Get Error Details
  3. Step 3: Check Context
  4. Step 4: Provide Actionable Output
  5. Notes
Original SKILL.md headings · 58 lines, 234 words
SKILL.md preview
---
name: debugging-dags
description: 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".
---

# DAG Diagnosis

You are a data engineer debugging a failed Airflow DAG. Use the extension tools to identify root cause and provide actionable remediation.

## Step 1: Identify the Failure

If a specific DAG was mentioned:
- Use `get_dag_runs` to find recent failed runs
- If the latest failed run is sufficient, use `analyse_dag_latest_run`

If no DAG was specified:
- Use `get_failed_runs` to list recent failures across DAGs
- Ask which DAG to investigate further

## Step 2: Get Error Details

Once a failed run is identified:
1. Use `analyse_dag_latest_run` or `get_dag_run_detail`
2. Focus on the failed task logs in the analysis
3. Categorize the failure:
   - Data issue
   - Code issue
   - Infrastructure issue
   - Dependency issue

## Step 3: Check Context

Gather context to understand why this happened:
- Compare with prior runs using `get_dag_runs` or `get_dag_history`
- Review DAG code via `get_dag_source_code`
- Check current system status using `go_to_server_health_view`

## Step 4: Provide Actionable Output

Structure your diagnosis as:

### Root Cause
Be specific about what failed and why.

### Impact Assessment
- Which tasks or outputs are affected
- Whether downstream consumers are blocked

### Immediate Fix
Concrete steps or code changes.

### Prevention
Data checks, retries, alerting, or code hardening.

### Rerun Guidance
- Trigger a rerun using `trigger_dag_run`

## Notes

- Use `go_to_dag_log_view` when a deep log inspection is needed.
- Avoid CLI commands for Airflow inspection.

Versions

RepositoryScoreLicence
This page · necatiarslan/airflow-vscode-extension90Apache-2.0
astronomer/agents100Apache-2.0
420company/artemis95MIT

Database snapshot: 13.11.2026 · package version 2c656bb1a244 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90testing-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".
  • 95authoring-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.
  • 90authoring-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.
  • 100authoring-dags
    Workflow and best practices for writing Apache Airflow DAGs. Use when creating a new DAG, write pipeline code, handling questions about DAG patterns and conventions or extending an existing DAG with a follow-up/downstream task. ANY request shaped like 'add a DAG named X', 'write…
  • 95testing-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". For simple test requests ("test dag", "run dag"), the airflow entrypoint…
  • 100testing-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". For simple test requests ("test dag", "run dag"), the airflow entrypoint…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.