I find it a little odd that, e.g., the "Constant fields" rule and the "Static readonly fields" rules seem to take precedence over the "Instance field (not public)" and "Static field (not public)" rules (respectively). This means for instance, that I get a warning about a static readonly field that I've named with a leading underbar (e.g. _myField), and the suggestion to rename it to MyField, when in fact it's a backing field for a public static property that already has that name.
To my mind, the fact that fields are private is more important in this context that that they're constant or readonly. It seems that you can control priority among user-defined rules, but (according to a simple experiment that I did) all the user-defined rules are lower priority than the predefined ones. Seems unnecessarily painful. Why not keep them in a single list, the order of which I can control? Or am I missing some useful aspect of this arrangement?