Fair points you are raising on the soft skills around code reviews. I knew a guy who was saying, “it’s about the code and not the developer”, which I honestly don’t like. Behind these pull requests, there is someone sitting who is, hopefully, caring about their work and is attached to what they produce.

The other side for the reviewers would be to raise a pull request themselves if the change they are seeking, goes beyond the scope of current pull request at review.

Finally, I think it matters that apart from the technical standards we should set at the team level (like you pointed out), we create a culture of safe and constructive code-review culture, which is not about attacking, but supporting the writer of the code in their work.