| name | drupalorg-issue-summary-update |
| description | Fetches a Drupal.org issue with all its comments and analyses whether the "Proposed resolution" in the issue summary matches the current discussion consensus. Drafts an updated summary for the user to paste back.
|
/drupalorg-issue-summary-update
Purpose: Ensure a Drupal.org issue summary's "Proposed resolution" reflects
the latest discussion in the comments.
Usage: /drupalorg-issue-summary-update <nid>
Instructions
Step 0: Detect issue type
If <nid> looks like a GitLab work item reference — a URL containing
git.drupalcode.org, or a shorthand like ai_context#3586157 — stop immediately
and tell the user:
"GitLab work items don't use the Drupal.org issue summary format (Problem/Motivation,
Proposed resolution, etc.). This skill only applies to Drupal.org issues."
Do not proceed further.
Step 1: Fetch issue with comments
drupalorg issue:show <nid> --with-comments --format=llm
Report to the user:
- Issue title, status, project
- The current "Proposed resolution" section (extracted from the body)
- A concise summary of what the comments discuss, highlighting the latest direction
Note: Comments from the automated "System Message" user (bot posts about
MRs being opened/closed) are automatically excluded from the output.
[PAUSE] Present your analysis:
- What the proposed resolution currently says
- Where comments agree, diverge, or add new direction
- Which parts of the summary may be out of date
Ask: "Would you like me to draft an updated issue summary?"
