Menu
Check and fix Drupal PHP coding standards violations using PHPCS and PHPStan. Use this skill when you need to validate code against Drupal standards, fix coding style issues, or run automated code quality checks.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | drupaltools-coding-standards |
| description | Check and fix Drupal PHP coding standards violations using PHPCS and PHPStan. Use this skill when you need to validate code against Drupal standards, fix coding style issues, or run automated code quality checks. |
Check and fix PHP code against Drupal coding standards using PHPCS and PHPStan.
Use this skill when:
| Tool | Purpose | Package |
|---|---|---|
| PHPCS | Code style (Drupal, DrupalPractice) | drupal/coder |
| PHPStan | Static analysis | phpstan/phpstan |
| PHPCBF | Auto-fix style issues | squizlabs/php_codesniffer |
# Check PHPCS
vendor/bin/phpcs --version 2>/dev/null && echo "phpcs_available"
# Check PHPStan
vendor/bin/phpstan --version 2>/dev/null && echo "phpstan_available"
vendor/bin/phpcs --standard=Drupal,DrupalPractice --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md,yml
vendor/bin/phpstan analyse --no-progress --error-format=table
vendor/bin/phpcbf --standard=Drupal,DrupalPractice --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md,yml
| Issue | Command |
|---|---|
| Line length | PHPCBF auto-fixes |
| Indentation | PHPCBF auto-fixes |
| Trailing whitespace | PHPCBF auto-fixes |
| Missing docblocks | Manual fix required |
FILE: src/Controller/MyController.php
--------------------------------------------------------------------------------
FOUND 3 ERRORS AFFECTING 3 LINES
--------------------------------------------------------------------------------
2 | ERROR | [x] Missing file docblock
15 | ERROR | [ ] Line exceeds 80 characters
42 | ERROR | [ ] Missing function docblock
FILE: my_module.module
--------------------------------------------------------------------------------
FOUND 1 WARNING AFFECTING 1 LINE
--------------------------------------------------------------------------------
23 | WARNING | [ ] Unused variable
------ -------------------------------------------------------------------
Line src/Controller/MyController.php
------ -------------------------------------------------------------------
23 Call to an undefined method Drupal\Core\Entity\EntityInterface::foo().
------ -------------------------------------------------------------------
[ERROR] 1 error
| Rule | Standard | Fix |
|---|---|---|
| Line length | Max 80 chars | Wrap line |
| File docblock | Required | Add file-level docblock |
| Function docblock | Required | Document all functions |
| Indentation | 2 spaces | Use spaces |
| Class names | PascalCase | Follow naming |
| Function names | camelCase | Follow naming |
composer require --dev drupal/coder phpstan/phpstan
✅ CODING STANDARDS CHECK COMPLETE
PHPCS Results: 2 errors, 5 warnings
Errors:
- src/Controller/MyController.php:45 - Line exceeds 80 characters
- src/Plugin/Field/MyField.php:78 - Missing function docblock
Warnings:
- my_module.module:12 - Unused variable $foo
- my_module.module:23 - Line indented with tabs
PHPStan: 0 errors
Auto-fix available: Yes
Run: vendor/bin/phpcbf --standard=Drupal,DrupalPractice
When checking coding standards in a Drupal project, first check if tools are installed:
# Check if composer dependencies exist
ddev composer validate 2>/dev/null && echo "vendor_exists" || echo "run composer install first"
Then run tools via DDEV:
# PHPCS via DDEV
ddev exec vendor/bin/phpcs --standard=Drupal,DrupalPractice --extensions=php,module,inc,install,test,profile,theme
# PHPStan via DDEV
ddev exec vendor/bin/phpstan analyse
# Auto-fix via DDEV
ddev exec vendor/bin/phpcbf --standard=Drupal,DrupalPractice
If vendor doesn't exist, run ddev composer install first.
Drupal projects include linting configuration for JS/CSS. Check these files:
| File | Purpose |
|---|---|
.editorconfig | General code style |
.eslintrc.json | JavaScript linting |
.stylelintrc.json | CSS/SCSS linting |
.prettierrc.json | Code formatting |
web/core/.eslintrc.json | Core JS config |
For PHP symbol navigation (classes, methods, references, inheritance), use LSP tools before grep:
php-lsp pluginhttp://localhost:64342/ssenpx cclsp@latest setup --userUse LSP for:
Run the project markdownlint script in a Drupal project and fix the reported markdown violations. Use this skill whenever the user asks to run markdownlint, lint markdown, check the docs, or says "run scripts/markdownlint.sh and fix the errors".
Run PHPCS in a Drupal project and fix the reported coding standards violations. Use this skill whenever the user asks to run phpcs, check coding standards, fix code style errors, lint PHP/Drupal code, or says things like "run phpcs and fix the errors" or "clean up my coding standards".
Run PHPStan static analysis in a Drupal project and resolve the reported errors. Use this skill whenever the user asks to run phpstan, run static analysis, fix type errors, or says "run phpstan and fix the errors".
Run the custom PHPUnit test suite in a Drupal project and fix the reported failures and errors. Use this skill whenever the user asks to run phpunit, run the tests, run the custom testsuite, or says "run phpunit and fix the errors".
Estimate costs and timeline for Drupal projects using a structured breakdown of tasks, roles, content types, and development work. Use this skill when the user asks for a project quote, cost breakdown, timeline estimation, budget planning, or resource allocation for a Drupal website. Trigger for requests like "how much would this Drupal project cost", "estimate this project", "create a quote", "plan the budget", or any discussion about pricing/timeline for Drupal development.
Create a Drupal.org issue title and summary body that is ready to paste into the issue form. Use when the user asks to draft, improve, or rewrite an issue from a bug report, feature request, patch, MR, commit, or discussion. When the user says "issue title", "issue body", "issue summary", or similar.