drupal-contribute-fix

Scan drupal.org for existing fixes before generating local patches.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps you triage Drupal contrib/core bugs by automatically searching upstream drupal.org for existing fixes before generating local patches, saving time and preventing duplicate work.

Core Features & Use Cases

  • COARSE: It performs upstream preflight searches, identifies upstream fixes, and determines whether to use MR or patch workflows based on the findings.
  • It downloads and checks baseline repos, copies changes into a baseline checkout, and generates a local diff artifact ready for MR submission.
  • It outputs a REPORT.md and ISSUE_COMMENT.md to facilitate downstream collaboration and handoff to maintainers.

Quick Start

Run the package command with your changed path to generate an upstream-aware MR-ready diff and contribution artifacts.

Frequently Asked Questions about drupal-contribute-fix

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

FAQPage Schema
How do I check for existing upstream Drupal fixes before creating a local patch?

The skill scans drupal.org for active merge requests and patches, identifying existing upstream fixes to prevent duplicate work before you generate a local patch for contrib or core bugs.

What is the best way to generate an MR-ready diff for a Drupal contrib module?

The skill downloads a baseline repo checkout, copies your local changes into it, and generates a local diff artifact specifically formatted for upstream merge request submission.

How does an MR-first workflow compare to a traditional patch workflow for Drupal core contributions?

An MR-first workflow submits via merge requests on drupal.org, while a patch workflow generates diff files; this skill automatically determines which approach to use based on current upstream activity.

Can I use this workflow for both Drupal core and contrib module changes?

Yes, the workflow applies to both Drupal core and contrib modules, resolving baseline information and generating patches across docroot/core and web/modules/contrib directory paths.

How do I document Drupal bug fixes for downstream collaboration with maintainers?

To document Drupal bug fixes for maintainer collaboration, the skill automatically generates a REPORT.md and an ISSUE_COMMENT.md file summarizing triage results and diff artifacts.

When should I avoid generating a local patch for a Drupal upstream bug?

You should avoid generating a local patch when the upstream preflight search finds an active fix on drupal.org, indicating you should follow the existing MR-first workflow instead of duplicating effort.