I don’t think code review tone matters much.<p>What’s important is to do a review quickly (ideally within couple hours, not days). It’s important to accept the pr even if it’s not perfect. It’s important to not force a developer rewrite a lot of code to implement a minor feature.<p>This tool doesn’t help with these common code review problems.<p>The worst experience I had in my career in my previous team when reviewer was perfectly polite, but ate my brain. For example, he refused to review single prs, he only reviewed complete two week work stacks, and often responded with “suggestion” to slightly rewrite the bottom pr (and I had to spend hours rebasing it). Or even “suggested” better approach when I had to throw away two week work. His comments tone were very positive and kindly.