Co-founder here! That's a valid point of course and I agree that it's hard to check for the "why" using automated tools and without prior knowledge of the progr

Co-founder here! That's a valid point of course and I agree that it's hard to check for the "why" using automated tools and without prior knowledge of the programmers intentions. However, it is absolutely possible to take your own idea of "good code" and translate it to a set of custom code checking rules in our tool, which you can then enforce automatically throughout all of your projects. So as long as you know what "good code" is for you and how it should look you can automate the checking. You can also share your own code patterns with other users btw so that they can use them in their projects, and you can use rules created by other users. Crowd-sourced code quality so to say :) Feedback is highly welcome btw since it's still a pretty early version of our product, so if you have comments, bug reports, suggestions or feature requests feel free to get in touch with us (@quantifiedcode, andreas@quantifiedcode.com)