Have you talked with the reviewers about this?

When I've seen this happen it usually boils down to communication problems. The solution is often to talk to the reviewers _before_ writing the PR.

For example,

1. Disagreement about the problem/solution - hash out the design first, then write the code

2. Disagreement about priorities - align expectations before investing too much time in design or code

3. (etc)

Yes, communication is hard. Unfortunately, it's really the only way to get things done with other people. Building decent communication skills is a worthwhile investment for all SWEs

Piggybacking this to say I will never be extremely productive when all my job boils down to is shifting code from one place to another, or building yet another braindead CRUD endpoint. My mind begins to wander and think about other things. I hear a lot of "we want to use our engineers in the best way possible" only to put people on mind-numbing zero-thinking framework guided work that doesnt capitalize on any of the traits of a good engineer. Before the frothing at the mouth business-minded people start saying "creative engineers are dangerous" I would suggest you actually go talk to your engineers. I doubt they say they want to greenfield a production idea in haskell. What they want is something that isn't the programming equivalent of a box ticking TPS report.

Your purpose is to serve the code reviewer, manager, and execs so that they can achieve their career and monetary goals.