dx-doctor

Diagnose dx workflow configuration files and installed plugin versions.

6|3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dx-doctor
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-core/skills/dx-doctor
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It identifies and reports health issues in the dx workflow configuration across all installed plugins, ensuring the setup is healthy after upgrades or changes.

Core Features & Use Cases

  • Validates configuration integrity, plugin presence, and version alignment to prevent silent failures.
  • Scans core files, seed data, and automation-related artifacts to surface misconfigurations and drift.
  • Use Case: After a plugin upgrade, run the doctor to detect outdated or missing components and receive remediation guidance.

Quick Start

Run the dx-doctor to generate a comprehensive health report for your current workspace.

Frequently Asked Questions about dx-doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check dx workflow configuration health after a plugin upgrade?

Run a doctor diagnostic to validate dx workflow configuration integrity, file presence, and plugin version alignment across dx-core, aem, seed-data, and automation, preventing silent failures after upgrades or changes.

What is dx workflow health validation and how does it work?

Dx workflow health validation is a read-only diagnostic process that scans core files, seed data, and automation artifacts to surface misconfigurations and version drift, providing actionable remediation guidance without modifying configurations.

Can I diagnose dx-core and automation plugin issues without modifying files?

Yes, you can diagnose plugin issues using read-only validation that enforces file presence and checks plugin versions, providing actionable remediation guidance without altering existing configuration files.

What's the best way to detect misconfigurations and drift in seed-data and automation artifacts?

The best way to detect drift is to run a diagnostic health check that scans seed-data and automation artifacts, validating configuration integrity and surfacing outdated or missing components for remediation.

Why does dx workflow validation fail to detect silent failures after changes?

Dx workflow validation might miss silent failures if configuration integrity, plugin presence, or version alignment are not thoroughly checked, making a comprehensive doctor scan necessary to surface misconfigurations and drift.