Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From drupal-lab
Browse and list Drupal.org project issues via RSS feeds. Use when the user wants to explore, list, or discover issues for a Drupal project -- e.g. "show me open Drupal core issues", "what issues exist for settings_tray", "browse drupal.org issues", "find critical Drupal bugs". Works with any project (core or contrib). Do NOT use for deep analysis of a single issue -- use drupal-lab:analyze-issue instead.
npx claudepluginhub cosmicdreams/claude-plugins --plugin drupal-labHow this skill is triggered — by the user, by Claude, or both
Slash command
/drupal-lab:browse-drupal-issuesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Browse Drupal.org project issue queues using RSS feeds for quick discovery and filtering.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Share bugs, ideas, or general feedback.
Browse Drupal.org project issue queues using RSS feeds for quick discovery and filtering.
browse-drupal-issues [project-name] [options]
project-name is optional — when omitted, the project is auto-detected from the current working directory and the status defaults to Open.
Options:
--status=<status> - Filter by issue status (e.g., Open, Fixed, Closed, Active)--priority=<priority> - Filter by priority (e.g., Critical, Major, Normal, Minor)--component=<component> - Filter by component (e.g., settings_tray.module or just settings_tray)--limit=<number> - Limit number of results to display--output=json - Output as JSON instead of human-readable text# No arguments — auto-detect project from CWD, show open issues
browse-drupal-issues
# Browse all open Drupal core issues
browse-drupal-issues drupal --status=Open
# Filter by specific component (settings_tray)
browse-drupal-issues drupal --component=settings_tray.module --status=Open
browse-drupal-issues drupal --component=settings_tray --status=Open # .module extension optional
# Find critical priority issues
browse-drupal-issues drupal --priority=Critical --limit=5
# Combine filters for precise results
browse-drupal-issues drupal --component=block.module --status=Open --priority=Major
# Browse issues for a contrib module
browse-drupal-issues views --status=Active
# Get JSON output for processing
browse-drupal-issues cloudflare --output=json
When project-name is omitted, the script resolves it in this order:
DRUPAL_MODULE_MACHINE_NAME env var (set automatically in DDEV contrib projects)*.info.yml file with type: module or type: theme in CWD or parent directorycomposer.json with a drupal/* package nameCLAUDE.md containing a **Module**: <name> lineThe detected name is printed to stderr so you can confirm it.
Execute the bundled Python script that:
https://www.drupal.org/project/issues/rss/{project}python3 scripts/fetch_drupal_rss.py [project] [options]
This skill pairs with the /analyze-issue skill:
Workflow: Browse to find issues, then analyze specific ones for implementation.
settings_tray.module) or short names (extension added automatically)categories=1 parameter (automatically added by the script)The script constructs URLs like:
https://www.drupal.org/project/issues/rss/drupal?status=Open&categories=1&component=settings_tray.module
Key parameters:
status - Issue status filtercategories=1 - Required for component filteringcomponent - Full module name (e.g., settings_tray.module)