drupal-coding-standards

You can enforce Drupal coding standards by running PHPCS with Drupal and DrupalPractice rules alongside PHPStan static analysis. This validates your custom codebase against established conventions for naming, class declarations, and structure.

The best way to run PHPStan and PHPCS for Drupal 10 modules is during pre-commit, CI workflows, or code reviews. This applies static analysis and style checks to ensure modules adhere to established quality patterns before deployment.

Yes, this supports Drupal 11 custom codebases. It applies guardrails for naming conventions, class declarations, and code structure specific to Drupal 10 and 11, performing static analysis to ensure consistent quality across modules.

Yes, you need Drupal coding standards tooling configured in your project beforehand. This includes PHPCS with Drupal standards and DrupalPractice rules, plus PHPStan, to perform the required static analysis and style checks.

Drupal modules fail coding standards checks due to style violations caught by PHPCS or type safety issues found by PHPStan. Running these tools identifies naming convention errors, improper class declarations, and structural problems in your code.

Yes, you can use this for DrupalPractice checks in a CI workflow. It supports running PHPCS with DrupalPractice rules and PHPStan analysis in pre-commit, CI, and code-review contexts to validate code quality before submission.