菜单
Drupal coding standards for quick checks and detailed file-type reviews. Covers PHPCS, PHPStan, naming conventions, code style enforcement, and comprehensive per-file-type standards for PHP, JavaScript, CSS, Twig, YAML, SQL, and markup in Drupal 10/11 projects.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
REQUIRED when user mentions a Drupal module + error/bug/issue - even without stack traces. Trigger on: (1) "<module_name> module has an error/bug/issue", (2) "Acquia/Pantheon/Platform.sh" + module problem, (3) any contrib module name (metatag, webform, mcp, paragraphs, etc.) + problem description. Searches drupal.org BEFORE you write code changes. NOT just for upstream contributions - use for ALL local fixes to contrib/core.
Draft a drupal.org issue comment after reproducing or investigating a bug. Use when the user has finished reproducing an issue and wants to write up findings as a comment on the d.o issue queue. Covers screenshot capture, HTML formatting for the d.o comment box, and conversational tone.
Full workflow for reviewing/reproducing a drupal.org issue. Invoke with `/drupal-issue-review <issue-url-or-number>`. Reads the issue, determines required Drupal core + module versions, scaffolds a fresh environment, reproduces the bug, and optionally drafts a comment. Companion to drupal-contribute-fix (which handles the actual fix + MR packaging).
Generic entry point for working on any drupal.org issue. Invoke with `/drupal-issue <issue-url-or-number>`. Reads the issue and all comments carefully, figures out what kind of action is needed, and either handles it directly or delegates to the right companion skill. Covers: bug reproduction, version bumps, MR adaptation, comment replies, reviews, cherry-picks, porting between branches, and general triage.
Hook implementations, service/DI patterns, and security patterns for Drupal 10/11. Use when implementing hooks, form alters, event subscribers, creating services, working with dependency injection, or reviewing code for security issues.
Update, refactor, audit, or create Claude Code skills in this workspace. Use when the user says "update the X skill", "add a gotcha to Y", "refactor skill Z", "create a new skill for W", "my skills are getting bloated", "audit my skills against the spec", or when a session has produced rules, patterns, or incidents that should be codified into existing skills. Covers agentskills.io spec compliance (name, description, line limits), progressive disclosure, Gotchas sections, Rationalization Prevention tables, file layout conventions, and the bloat patterns learned from maintaining this workspace's Drupal skills.
| name | drupal-coding-standards |
| description | Drupal coding standards for quick checks and detailed file-type reviews. Covers PHPCS, PHPStan, naming conventions, code style enforcement, and comprehensive per-file-type standards for PHP, JavaScript, CSS, Twig, YAML, SQL, and markup in Drupal 10/11 projects. |
| metadata | {"author":"ajv009, ronaldtebrake","version":"1.0"} |
Announce at start: "I'm using the drupal-coding-standards skill to review [file type] code."
IRON LAW: ALWAYS RUN PHPCS BEFORE COMMITTING. Never skip static analysis.
Always run PHPCS before committing. Never skip static analysis. Use declare(strict_types=1) in every PHP file. Prefer final classes unless explicitly designed for extension. Avoid deep nesting; use guard clauses and early returns.
Activate this skill when:
This skill uses dynamic context discovery to load only the relevant standards based on the file type being reviewed:
.php, .js, .css, .twig, .yml, etc.)standards-index.md to find the corresponding standard fileassets/standards/[category]/[file].mdFor the full routing table mapping file extensions to standard files, see standards-index.md in this skill directory.
assets/standards/accessibility/accessibility.md (applies to all frontend code)assets/standards/spelling/spelling.md (applies to all documentation and user-facing strings)For validation commands, naming conventions, required code patterns, anti-patterns, and module structure: see references/quick-reference.md