Skip to content
required PHP Coding Standards
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

required PHP Coding Standards

required coding standards for PHP, inspired by the Human Made Coding Standards project.

For JS coding standards head over to wearerequired/eslint-config.


  1. composer require --dev dealerdirect/phpcodesniffer-composer-installer wearerequired/coding-standards
  2. Run the standards checks using the following command:
vendor/bin/phpcs .

The final . here specifies the files you want to test; this is typically the current directory (.), but you can also selectively check files or directories by specifying them instead.

You can add this to your Travis CI configuration as a test:

  - phpunit
  - vendor/bin/phpcs .

Bonus: To make things easier, you can add something as follows to your composer.json file:

	"scripts": {
		"format": "vendor/bin/phpcbf --report-summary --report-source .",
		"lint": "vendor/bin/phpcs --report-summary --report-source ."

After that, run composer lint to run the standards checks and composer format to try auto-fixing of errors and warnings.

Excluding Files

This standard includes special support for a .phpcsignore file (in the future, this should be built into phpcs itself). You can place a .phpcsignore file in your root directory (wherever you're going to run phpcs from).

The format of this file is similar to .gitignore and similar files: one pattern per line, comment lines should start with a #, and whitespace-only lines are ignored:

# Exclude our tests directory.

# Exclude any file ending with ".inc"

Note that the patterns should match the PHP_CodeSniffer style: * is translated to .* for convenience, but all other characters work like a regular expression.

Patterns are relative to the directory that the .phpcsignore file lives in. On load, they are translated to absolute patterns: e.g. */tests/* in /your/dir/.phpcsignore will become /your/dir/.*/tests/.* as a regular expression. This differs from the regular PHP_CodeSniffer practice.


You can create your own custom standard file (e.g. phpcs.xml.dist) if you want to extend these coding standards:

<?xml version="1.0"?>
	<!-- Use required Coding Standards -->
	<rule ref="Required"/>

	<!-- Your custom rules go here -->

You can then reference this file when running phpcs:

vendor/bin/phpcs .

Included Checks

The phpcs standard is based upon the WordPress-Core, WordPress-Docs, and WordPress-Extra rules from the WordPress Coding Standards. It also uses VariableAnalysis for problematic variable use and some SlevomatCodingStandard rules from the Slevomat Coding Standard. Most of the sniffs are also providing automatic errors fixing for phpcbf.


The EditorConfig standard helps developers define and maintain consistent coding styles between different editors and IDEs. This way it's easier to follow the given coding standards in a project, without the need to fiddle with IDE settings.

The recommended .editorconfig file for a WordPress project looks like this:

root = true

charset = utf-8
indent_style = tab
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true

trim_trailing_whitespace = false

indent_style = space
indent_size = 2
You can’t perform that action at this time.