Description: ------------ There is a way to define custom ruleset but there is no word about what rules are available and what properties they have. And developers are supposed to google on some hints, use someone's pieces, read source code in order to understand how how use this or that rule, or in order to find a rule needed. This is just stupid. Was it so hard to put a small txt file with the list of rules and their properties?

Next time, try asking nicely. It makes people more likely to respond favourably to your requests. But yes, this is something I've been wanting to do for a while but have not yet had the time. I will certainly get to it eventually, but it depends on my other commitments. Ideally, I'd like to create a script to parse the sniffs for public variables and use their comments to generate the docs.

Hello Greg, thank you for such a quick response. I'm sorry about my tone, it's nothing personal, but I was really badly surprised when noticed that one of number one tools is almost impossible to use. I mean, it's a tool of a large scale, used worldwide by huge community, and that was my first impression because I'm new to PHP world, and after spending about 4 hours trying to find any information while being on tight schedule, I just got angry. Also I wouldn't be so rude if I knew you work on this tool alone, I just saw a list of developers, 766 people, and it just looked to me as a truly neglectfulness when such a big community of developers cannot take care about such a simple stuff. Sorry me again, and thank you for creating such a useful tool.

Thanks Alexander. I understand the frustration. It truly is on my todo list, as is the complete migration of all documentation to the github wiki (it is partially done).