At FullStory, we use clang-format to format protobuf code. And we have a custom linter for catching some other style issues, outside of just formatting.
The clang-format tool doesn't have a ton of options for protos, but it's been good enough for our purposes. It can get confused when you have complicated custom options -- like message options, where you put a long message literal as the value -- which can lead to less-than-stellar results, aesthetically speaking.
But having a standard with some warts seemed better than no standard...