[CraigJPerry]

I think that's a bit harsh.

Of course we write style guides and while I like the idea that it's part of the tool, that's rarely the case.

I don't follow the objection about a colleague helping ensure consistency across a team. I'm really not sure why competence comes into that equation either.

Agree with the idea any style guide should be automated. Several CI servers I know of can incorporate style checkers and their reports into their workflow so this can be made really hands off, even to the point of automatically failing code review stage before its been lumped in the review queue.

Don't agree at all with the idea this type of doc should be rejected. In fact it's completely wrong to jump into automation without having "found which way is up" manually first time around.