wp-coding-standardslisted

# WordPress Coding Standards (PHPCS + WPCS) > **Model note:** Setup and config steps are mechanical (`haiku`). Fixing sniff violations across many files works fine on `haiku`. Only reach for `sonnet`/`opus` when violations involve subtle logic (e.g. escaping inside complex SQL builders). Configure and enforce the WordPress Coding Standards via PHP_CodeSniffer. WPCS is required for WP.org submission and is the canonical style guide for all WordPress PHP code. ## When to use - "Set up PHPCS for my plugin", "add WordPress coding standards", "configure phpcs.xml". - "Fix sniff violations", "run phpcbf", "auto-fix coding standards". - "Add PHPCS to GitHub Actions / CI". - "Why is PHPCS flagging X?", "suppress a false-positive sniff". - Pre-submission audit: "is my code style WP.org–compliant?" **Not for:** PHPStan static analysis or type checking — use `wp-phpstan-stubs`. Security auditing beyond style issues — use `wp-plugin-audit`. ## Method ### 1. Install ```bash composer require --dev squizlabs/php_codesniffer wp-coding-standards/wpcs dealerdirect/phpcodesniffer-composer-installer ``` Current **WPCS is 3.1** (July 2026) — requires PHP 7.4+ and PHP_CodeSniffer 3.9+. Leave the requirement unpinned (as above) or pin `wp-coding-standards/wpcs:"^3.1"`; the 3.x line recognizes pluggable functions and reserved post types through WP 6.4/6.5 and defaults `minimum_supported_wp_version` to 6.2. `dealerdirect/phpcodesniffer-composer-installer` auto-registers WPCS paths so no man