dx-upgrade

Automate dx workflow upgrades with dx-doctor diagnosis and auto-fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading a consumer project's dx workflow to the latest plugin versions is error-prone and time-consuming. This Skill automates diagnosis, auto-fixes plugin-owned files, migrates configuration, and reports required manual actions.

Core Features & Use Cases

  • Diagnose issues with dx-doctor and generate an upgrade plan.
  • Apply auto-fixes for stale or missing plugin-owned files and migrate configuration.
  • Scope the upgrade to dx, aem, auto, or all plugins and report remaining tasks.

Quick Start

Run /dx-upgrade all to diagnose with dx-doctor and auto-fix plugin-owned files across the project.

Frequently Asked Questions about dx-upgrade

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

FAQPage Schema
How do I automate upgrading consumer project workflows to the latest plugin versions?

Automating consumer project workflow upgrades involves diagnosing issues with dx-doctor, applying auto-fixes for plugin-owned files, migrating configuration, and installing missing assets across targeted scopes.

Can I scope a dx workflow upgrade to specific plugins like dx or aem?

Yes, workflow upgrades support scope control using dx, aem, auto, or all targets, allowing you to limit configuration migration and auto-fixes to specific plugin sets.

What is the best way to migrate configuration and fix stale plugin-owned files during an upgrade?

The best way to migrate configuration and fix stale plugin-owned files is to run an automated upgrade that diagnoses issues, applies auto-fixes, preserves user customizations, and reports remaining manual actions.

Does the automated upgrade process preserve my customizations in plugin-owned files?

Yes, the automated upgrade process preserves user customizations while applying auto-fixes to stale or missing plugin-owned files and migrating configuration across the targeted scopes.

Why do I still have manual actions remaining after running an automated project upgrade?

Manual actions remain after an automated upgrade because the tool reports required tasks that cannot be auto-fixed, ensuring user customizations are preserved while safely migrating configuration and plugin resources.