Code review tags
https://conventionalcomments.org/ is something I have found to be very useful. Instead of just free styling each code review comment, you tag it up according to a template.
When you get a comment like;
Question (non-blocking, showerthought): Should we do this change globally or only in this module?
You directly understand that the person reviewing is asking of this code change is applicable in other places, and that it’s a discussion point. It could lead into a back and forth on design choices based on the answer. That could in turn end up with being a suggestion for a code change. But, non-blocking means that the discussion can be deferred or replied to with “lets bring it up next time we have a backend wide talk” or whatever.
I give this system a warm recommendation and the examples in the post linked are good enough to get going. What I noticed after a while was that standardising on these, meant no other docs where needed seeing how it is very well explained too. The only thing I added is showerthought and that tag is only used in the right context, mostly if I and that dev are on a mission together and something they did sparked a thought on how to solve the greater mission.