(This page needs expanded installation instructions, especially for Windows-based systems.)
This is a custom coding standard for the PHP CodeSniffer that attempts to codify and enforce the Joomla coding standards.
The reasons seem obvious, but one look at reality shows they aren't, so I'll enumerate some of them here:
- Coherent and consisting coding practice makes the files look more professional. Conflicting styles in the same project (or worse, the same file) not only look sloppy, they encourage further sloppiness.
- When all code complies with the same standard, bad code is easier for everyone to spot.
- It makes it easier for someone new to a particular file in the project to find and fix errors, or extend functionality.
- If there is no consistent standard maintained, the sometimes developers will reformat the code to suit themselves. This causes a wide range of changes in the code repository, and if there is a later problem, a significant change could be lost in the chaff produced by a diff.
First you'll need to install phpcs (http://pear.php.net/package/PHP_CodeSniffer/download/). This set of files is intended to work with phpcs version 1.3, so behavior with any other version is undefined.
Then download and unzip the Joomla CodeSniffer, and copy the contents of it into /path/to/PHP_CodeSniffer/Standards/Joomla. (The path on some systems is /usr/lib/php/PHP/PHP_CodeSniffer but this varies from system to system. Use
pear config-get php_dir
to find out where the PEAR directory is on your system, then add "/PHP/PHP_CodeSniffer" to it.)
You invoke the custom standard by
phpcs --standard=Joomla --tab-width=4 file/to/sniff
Further documentation on the use of phpcs can be found at: 
left|thumb|200px|1) Eclipse PTI While everybody loves the console as it is with no doubt the most effective way to do whatever you need to do.. sometimes even linux gurus need a little bit of comfort.
Fortunately there is a plugin available for eclipse (tested) and netbeans (not tested) that integrates the CodeSniffer in our favorite IDE, so any coding standard violations are shown like "normal" errors (see screen shot 1).
Installation is a breeze and follows the usual pattern:
right|thumb|150px|2) Eclipse PTI settings You are now able to sniff for code violations against common standards like PEAR or Zend etc.
To sniff against your own standards, all you have to do is specify their location and activate them (see screen shot 2)