drupal-contrib-mgmt

Coordinate patch-based upgrades for Drupal contributed modules with Composer and validate compatibility before deployment.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/AJV009/drupal-devkit --skill drupal-contrib-mgmt-ajv009
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drupal-contrib-mgmt
Source: https://github.com/AJV009/drupal-devkit/tree/main/plugins/drupal-core/skills/drupal-contrib-mgmt
Command: npx skills add https://github.com/AJV009/drupal-devkit --skill drupal-contrib-mgmt-ajv009

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing Drupal contributed modules often requires juggling composer updates, patches, and compatibility checks across Drupal versions; this skill provides a structured workflow to streamline those tasks.

Core Features & Use Cases

  • Patch-based upgrade workflow using composer patches for Drupal contributed modules.
  • Guidance on version compatibility, patch sourcing, and lenient upgrade options.
  • Real-world use: Upgrading a module and applying a Drupal 11 compatibility patch to ensure core compatibility.

Quick Start

Configure and apply patches for a Drupal module upgrade, then run composer install to apply patches and validate the upgrade.

Frequently Asked Questions about drupal-contrib-mgmt

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

FAQPage Schema
How do I manage Drupal contributed module upgrades with Composer patches?

Managing Drupal contributed module upgrades involves coordinating composer updates, defining patch scopes, and verifying Drupal 11 compatibility. You configure patch definitions, apply them via composer install, and validate the upgrade before deployment.

What's the best way to apply a Drupal 11 compatibility patch to a contributed module?

Applying a Drupal 11 compatibility patch requires sourcing the patch, defining it in your composer patch definitions, and running composer install. This structured workflow ensures the contributed module maintains core compatibility across versions.

How do I verify patch provenance across multiple Drupal modules during an upgrade?

Verifying patch provenance during Drupal module upgrades requires documenting patch sources, validating dependencies, and tracking versions across multiple modules. This ensures patches are clearly sourced and applied correctly before testing.

Does this Drupal patch management workflow support lenient upgrade options?

Yes, the Drupal patch management workflow provides guidance on lenient upgrade options. This allows flexibility when coordinating version compatibility and patch sourcing for contributed modules during the composer upgrade process.

Why do I need to document dependencies and patches before deploying Drupal module updates?

Documenting dependencies and patches before deploying Drupal module updates ensures that upgrade steps are clearly validated and patch provenance is maintained. This structured approach prevents compatibility issues and enables testing before final deployment.

Can I use this workflow to coordinate updates across multiple Drupal contributed modules?

Yes, you can coordinate patch-based upgrades across multiple Drupal contributed modules. The workflow manages patch provenance, version compatibility, and dependencies for several modules simultaneously to ensure a validated deployment.