I see tests completing to the maximum the revision of the human code
Hmm of everything you say that seems to me the most. Your meaning may be nuanced, but always remember that the idea is to produce functional software, not well-coded software.
I would suggest that the first thing you do is write the rules for which you are reviewing the code. it is to say
- Coverage of unit tests 90%
- no gotos!
- BLA bla
Once you're done, everyone can do a code review pretty quickly. Maybe you can not capture everything you want to apply in a set of rules, but at least a lot of the work can be "outsourced"
Second, I suggest you completely stop the code reviews. Let the team decide what rules to apply and leave them free to modify, apply, or ignore them as they feel it works best for them.
Preserve the quality of your product by ensuring that non-functional requirements are defined when new features are offered.
This is a much stronger control than a code revision. If a page needs to be loaded in less than 3 seconds, AT charge in less than 3 seconds. If all the SQL code must be in SProcs in order to be verified, it is a requirement of the company.
But make sure to check that these are real requirements of the company.