Like Bugs and Potential Bugs, Coding Standards Breaches are tracked through the issues mechanism. While it's difficult to match each of the seven deadly coding sins to an analogous deadly spiritual sin, you might match this one to pride - pride that your might associate this sin with sloth - because transgressors are too lazy to learn and follow your team's standards about whether or not to use spaces in
if statements. But it may be more appropriate to match this coding sin to the moral sin of pride - pride that the sinner's code is so good you he don't need to be bothered with which line you and your teammates all agreed to put the curly brace on. Or you might tag it to sloth - because you're too lazy to learn and follow your team's standards about whether or not to use spaces in if statements.Either way
Another, perhaps more serious example of this type of sin is the failure to follow naming conventions. Flout the industry standards about naming constants in all upper case, and you invite the coders who come behind you to fall into the kind of subtle bug that can be very hard to diagnose.
Wherever the infraction falls on the curly brace-to-upper case continuum, this sin is about not following the team-agreed standards. And that lack of compliance means that other people on the team will be tripped up when they try to read this non-compliant code, and at best spend extra time just trying to parse out what's happening - time that could have been used for moving the code base forward.