> The Nitpicker's Gambit: The reviewer fixates on trivial style issues like whitespace, bracket placement, variable naming conventions etc. They make the developer conform perfectly to their preferred style, even if it's not specified in the team's coding guidelines.

Mostly solved by autoformatters. If your team refuses to use one, start collecting metrics on time wasted in those discussions, and present to management.

> The Silent Treatment: The reviewer provides no feedback at all for a long time after the review is requested, but does respond just often enough to keep the review "active". The author has to ping several times to get any response.

Set a policy of auto-approve in N days if no engagement.