skills/drupal-issue/SKILL.md
Create, update, or add comments to issues on drupal.org using a guided manual workflow. Invoke when user wants to create a bug report or feature request on drupal.org, says "create a drupal.org issue", "open a drupal issue", or uses /drupal-issue. Has side effects: creates publicly visible issues on drupal.org. Requires user to paste content and submit (CAPTCHA-protected). Also supports listing and updating issues.
npx skillsauth add kanopi/cms-cultivator drupal-issueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Create, update, and manage issues on drupal.org using a guided clipboard + browser workflow.
This skill creates publicly visible content on drupal.org:
Automation is not possible — drupal.org uses PerimeterX CAPTCHA protection. This guided workflow uses your authenticated browser session for reliable, CAPTCHA-safe submission.
/drupal-issue create {project} — Create new issue/drupal-issue update {project} {issue_number} — Update issue status/drupal-issue comment {project} {issue_number} — Add comment/drupal-issue list [{project}] — List issuesWhen Task() is unavailable:
For issue creation:
Gather issue details — Ask for: project name, issue type (Bug/Feature/Task), title, description, Drupal version, priority
Generate formatted HTML using official drupal.org template:
Bug Report:
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
{What's wrong?}
<h4 id="summary-steps-reproduce">Steps to reproduce</h4>
1. {Step 1}
2. {Step 2}
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
{How to fix it}
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
- [ ] Confirm the bug
- [ ] Write fix
- [ ] Add tests
<h3 id="summary-ui-changes">User interface changes</h3>
None
<h3 id="summary-api-changes">API changes</h3>
None
Display content — Show complete formatted issue for copy/paste
Provide URL — https://www.drupal.org/node/add/project-issue/{project}
Guide settings — Issue category, version, priority dropdowns to select
⛔ STOP: User pastes content, sets options, submits — then replies with issue number
Confirm success — Display: issue URL, number, next steps
When running in Claude Code with Task() available:
Task(cms-cultivator:drupalorg-issue-specialist:drupalorg-issue-specialist,
prompt="Execute the drupal-issue command with arguments: {arguments}. Generate properly formatted issue content using drupal.org HTML templates, copy the title to clipboard, open the issue form in the browser, and guide the user through submission. Request the issue number from the user after creation.")
The agent will:
tools
Strategist-focused site audit for discovery and pre-discovery. Given a site URL and optional qualitative research data, navigates the site via CoWork, audits against all 21 UX Laws from lawsofux.com, reviews content hierarchy, synthesises qualitative data, runs Lighthouse, and produces two deliverables — a Project Knowledge Summary (Markdown for Claude Desktop Projects) and a polished, iterable HTML Artifact for client sharing. Use when a strategist, UX lead, or PM asks for a discovery audit, UX laws audit, content hierarchy review, pre-discovery site review, "audit this site for strategy", "strategist audit", "UX audit", or pastes a site URL with discovery context. Not for developer audits — use accessibility-audit, performance-audit, or live-site-audit for those.
development
Provide story point estimation guidance with hour calculations for software development tasks. Uses Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, 34+) and converts story points to hours. Includes platform-specific adjustments and velocity calculations.
tools
Perform a full QA review of a Teamwork task by reading the task and all its comments for context, extracting the multi-dev URL, generating dynamic validation steps tailored to the task type, and using CoWork browser automation to execute those steps on the multi-dev environment. Produces a structured validation report with pass/fail per step, screenshots, internal notes, and a client-facing summary — all shown in chat. Use this skill whenever the user asks to QA, test, validate, or review a Teamwork task or multi-dev environment — even if they just say "can you QA this?" or paste a Teamwork link. Also triggers for phrases like "run QA on", "check the multi-dev", "validate this task", "test the dev link", or "review the ticket". Works across Drupal/CMS updates, WordPress/plugin updates, bug fixes, new feature development, and general web development tasks.
tools
Generate a client-facing project heartbeat / status update message for a Kanopi project, ready to be posted as a Teamwork message. Use this skill whenever the user asks to write, draft, generate, or send a project update, heartbeat, status update, or progress report to a client. Also triggers when the user says things like "time for a project update", "draft the heartbeat", "write up the update for [project]", or "it's been two weeks, let's send an update". Always use this skill — even if the user doesn't say "heartbeat" — whenever the intent is to summarise recent project activity for a client audience.