skills.rest
cosmicdreams
cosmicdreamsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

issue-summary

Generate a drupal.org contribution comment summarizing fixes and verification steps.

Updated Feb 28, 2026
Search Tags:#automation#issue tracker#drupal#git diff#contribution summary#testing instructions#obsidian archive
One-click install
npx skills add https://github.com/cosmicdreams/claude-plugins --skill issue-summary-cosmicdreams
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-summary
Source: https://github.com/cosmicdreams/claude-plugins/tree/main/drupal-lab/skills/issue-summary
Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill issue-summary-cosmicdreams

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a clear drupal.org contribution comment that explains what was fixed and gives reliable verification steps for the patch you just validated.

Core Features & Use Cases

  • Post-ready contribution summary: Converts the validation analysis report and the actual git diff into a structured maintainer-friendly comment.
  • Verification guidance: Produces step-by-step manual testing instructions (including cache clearing and where to click).
  • Change and coverage transparency: Lists changed files and summarizes automated test coverage (types, classes, and how to run them).
  • Guardrails: Enforces correct sequencing by warning not to use the skill before validation passes (run drupal-lab:validate-patch first).

Quick Start

Ask the AI to run drupal-lab:issue-summary after the reviewer stage finishes to generate the final drupal.org contribution comment and archive it to your Neurons vault.

Frequently Asked Questions about issue-summary

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

FAQPage Schema
How do I generate a Drupal contribution comment from a git diff?▼

To generate a Drupal contribution comment, the Skill reads your analysis report and git diff to produce a structured Markdown summary with changed files, manual test steps, and automated test coverage for maintainers.

What should a Drupal issue summary include for patch verification?▼

A Drupal issue summary should include a list of changed files, step-by-step manual testing instructions with cache clearing details, and a summary of automated test coverage explaining how to run the tests.

Do I need to validate my Drupal patch before generating an issue summary?▼

Yes, you must validate your patch first. The Skill enforces correct sequencing and warns not to generate the summary before validation passes, ensuring you only summarize verified code changes.

Can I use this to summarize merge request changes for a Drupal worktree?▼

Yes, it applies to Drupal issue and merge request workflows. It infers the worktree path from the issue number, reads the corresponding analysis report and diff output, and creates a ready-to-post summary.

How do I archive a Drupal contribution summary to an Obsidian vault?▼

After generating the contribution comment, you can archive the final Markdown summary directly to your Neurons Obsidian vault to maintain a record of the verified patch and its testing instructions.

Related Skills

Explore More Software Engineering Skills→
jiayaoqijiajiayaoqijia
98

fix

Generate minimal security patches as unified diffs with summaries and LOC counts.

Community
Advanced
cosmicdreamscosmicdreams

vault-store

Route AI-generated documents into an Obsidian vault with deterministic path rules.

Community
Advanced
mgiffordmgifford

drupal-contrib-mgmt

Manage Drupal module updates, patches, and Drupal 11 compatibility validation.

Community
Advanced
KangJiSseokKangJiSseok

code-review-pr-body

Generate structured pull request body drafts from git diff outputs.

Community
Advanced