I often use standard tools (e.g. lint, valgrind) or my own tools to help me compose a review. Recently, I suggested creating such tools as a possible Code Challenge.
There's no substitute for an experienced human looking at one's code, but promoting automated tools seems to me to be a good adjunct to Code Review's mission.
I should clarify that I would not be in favor of having bot-posted reviews, but I am in favor of helping programmers help themselves, such as with a list of tools and resources.
One possibility might be to add to the Help Center and describe how to turn on compiler warnings for various different compilers, assemblers, etc. and to give the suggestion that compiling cleanly without errors or warnings before posting code for review is a way to keep the signal-to-noise ratio on Code Review high.
