drupal-dev

Analyze a Drupal site's codebase to extract architectural patterns, design decisions, and transferable insights for professional growth. Produces a structured report with an executive summary, per-concern deep analysis, diagrams, and actionable lessons. Use when the user asks to understand a site's architecture, review design patterns, analyze how a codebase is structured, understand why decisions were made, or wants a high-level view of a Drupal project. Also trigger when the user mentions "architecture analysis", "site anatomy", "design patterns in this codebase", "architectural review", "how is this site built", "what can I learn from this code", or wants to study an existing codebase to grow as an architect.

Scan Drupal custom modules for deprecated API usage using upgrade_status. Installs the module temporarily if needed, runs the scan, reports findings by severity, then offers to remove the module. Use when user asks about Drupal deprecations, wants to check if custom code is ready for the next major version, or asks to run upgrade_status.

Drive the iterative red/green loop for Drupal code quality — run phpcbf → phpcs → phpstan on changed PHP files (or a user-specified target), fix mechanical violations in place, and rerun until clean. Use whenever the user wants to "tighten up", "clean up", or "lint and fix" their PHP changes before commit, says "run the quality loop", "phpcs and phpstan my changes", "drupal quality check", "loop phpcs until clean", or asks to "check my changes" in a Drupal/PHP context. Also use proactively after a chunk of PHP edits and before pushing/PR-ing, even if the user doesn't explicitly ask — surfacing style/static errors before the user has to do it is a strong default. Skip this skill when the user just wants ONE run of phpcs or phpstan and is going to read the results themselves.