Easily comply with Symfony2 coding style using CodeSniffer and PhpStorm Code Inspection

The goal of this article is to implement Symfony2 coding style in your PhpStorm editor. This will take you 5 minutes to configure your workspace.

Symfony2 CodeSniffer installation

You can follow this steps to install the Symfony2 standard CodeSniffer using Composer.

  1. Install phpcs:
    composer global require "squizlabs/php_codesniffer=1.*"

    You can follow the PHP_CodeSniffer documentation to include it in your project dependencies.

  2. Simply add the composer bin directory to your PATH in your ~/.bash_profile (or ~/.bashrc) by adding this line at the end of the file:
  3. Before use phpcs command, you must open a new shell or execute this command :
    source ~/.bash_profile
  4. UPDATE (27 Sept 2014): The OpenSky Standards I have used seems to be no longer available. I use this repo instead:
  5. Copy, symlink or check out the repo to a folder called Symfony2 inside the phpcs Standards directory:
    cd ~/.composer/vendor/squizlabs/php_codesniffer/CodeSniffer/Standards
    git clone git@github.com:escapestudios/Symfony2-coding-standard.git Symfony2
  6. Now, your list of installed coding standard should look like this:
    phpcs -i
    The installed coding standards are PSR1, PSR2, PHPCS, Zend, MySource, Squiz, Symfony2 and PEAR

PhpStorm configuration

  1. Configure PhpStorm to use phpcs

    Go to Project Settings (PHP > Code Sniffer). Use this command to find phpcs path: which phpcs and put the result on the PHP Code Sniffer path field. You can test your configuration by clicking on the validate button. Then don’t forget to click on the Apply button.

    phpcs configuration

  2. Configure PhpStorm inspection to use Symfony2 coding style

    Go to Project Settings (Inspection). Select PHP > PHP Code Sniffer validation inspection. In the right panel, you can choose your Coding standard. If Symfony2 does not appear in the drop-down list, click on the refresh button.

    inspection configuration

  3. Optional: Change the appearance of the inspection alerts

    Return in the PHP Code Sniffer inspection menu. Click on the button with three dots to Edit severities. In the new window, click on the + button to add a new one. Choose a name, PHPCS for example. And apply just a black background. You can do the same for warning validation.

  4. Enjoy!enjoy

A Pull Request return for Coding style error? Never!

I usually use the opensky Symfony2 coding style but what is yours?

You liked this article? You'd probably be a good match for our ever-growing tech team at Theodo.

Join Us

  • Dirk Luijk

    Nice article, thanks.

  • emilien

    The github link to opensky is broken

  • Robert Wildling

    Hi, thank you very much for this article!

    Unfortunately the OpenSky git repository seems to be no longer available. Which alternative do you recommend to use?

  • Robert Wildling

    AGain me – I actually had to install the repository to another location to make it work. The location on my Mac 10.9.4 is:

    Locate pear and get the php_dir:
    pear config-show | grep php_dir

    cd to that php_dir and move down to the folder PHP/CodeSniffer/Standards

    But then again: I use MAMP and changed ma path respectively…

  • Jonathan Beurel

    Hi Emilien and Robert.

    I’m currently looking for an alternative to the OpenSky Coding standards : https://twitter.com/JonathanBeurel/status/513987887717965824

  • Kevin S

    git clone git@github.com:lapistano/Symfony2-coding-standard.git Symfony2 requires the user to be authenticated,

    with :
    git clone https://github.com/lapistano/Symfony2-coding-standard.git Symfony2 not!

    Thanks for the tips!

  • Robert Wildling

    Hi, Jonathan,

    sorry,I read the note only today (no automatic mail information).

    Could you please check again, if your list up there mentioning TYPO3 really goes along with the Symfony2 standard? From what I saw, it absolutely does not.

    Thank you!

  • Thanks for the article! In our projects at LeapHub we also include our coding standard using composer, as we want a defined revision of the standard to be bound to every project.
    For this reason we started a fork of the Symfony2 standard of @lapistano as composer package several months ago.

    It has a stable v1.* where its usable with the PHP_CodeSniffer 1.* and the main branch was ported to PHP_CodeSniffer 2.* today. It might also be useful for one of you guys:



  • Tristan Roussel

    A note on configuration:

    When refreshing your Standards on Settings > Inspections, you may see the error “Can not retrieve available standards, check PHP Code Sniffer tool configuration.”. The error should help you understand the misconfiguration, but in case you’re stuck:

    To check the current config of phpcs, type “phpcs –config-show”. You’ll see the path where your Standards should be installed, if it’s not right you can reset it with “phpcs –config-set installed_paths my/standards/path”.

    By the way, you can use “phpcs –config-show” to know where to install new standards for unusual installations (Mac Homebrew phpcs installation may have Standards for example in /usr/local/etc/PHP_CodeSniffer/Standards, or in this thread Robert Wildling’s installation was in “php_dir”/PHP/CodeSniffer/Standards)


  • Pingback: Jenkins et symfony2 | Kaizendo.fr()