My answer is: you should not to monitor review comments at all.
- Try to trust to your team. It's help to avoid micromanagement (like monitoring review comments).
- If you are Project Manager, you should think about business. If you are Functional Manager, you should think about development process. But only developers (including tech lead and architect) should care about technical details (Code Review exactly about technical details). Technical competence of your development team should be much higher then yours. In other case, your development team have extremely low technical skills.
In additional, I can describe how we make Code Review in our team:
First of all, all developers are involved in Code Review. We use Git. When somebody create Pull Request from his fork to origin, every developer of our team should review and approve it. Pull Request should be approved by (amount of developers - 2) developers before merge.
This approach have two advantages:
Collective code ownership. Everybody knows what colleagues are doing. Everyone have knowledge about whole code. If somebody made a mistake, part of responsibility for it should take other team members.
Collective mind can find much more weak places and poor decisions in code.
Somebody might say that such approach would lead to eternal debates and conflicts. But I never had these problems in my practice.
You can ask more technical details in programmers.stackexchange.com.