Only 2 rules (Score 1)

The only rule I've ever seen that matters: if you modify a file, keep the file's style consistent. Either code to match the rest of the file or (if you are making enough of a change to justify it), reformat/refactor everything.

Other than that, as a lead or manager I list "stop words" that should tell a programmer to show the code to someone else and explain why they did something unexpected (goto, operator->*, returns nested deep in the middle of a function, etc.) and pick whatever naming and indenting standard is common on the platform, but don't get worked up over it.

And the #2 rule (after in-file consistency): no standards discussion in code reviews. If someone violates common standards, tell them separately. Otherwise reviews can turn into nit-picky "move this here and change that prefix" 3p33n waggles.