>>> If "usually" PRs result in code style or architecture discussions, I'd suggest you have a team problem, not a process one. Start with the humans. True, Why

>>> If "usually" PRs result in code style or architecture discussions, I'd suggest you have a team problem, not a process one. Start with the humans. True, Why is code being written without the architecture and initial design hashed out? Do an initial high level design, discuss with your team, hash out any issues, then start with the implementation. The PR code review should be a review of the implementation and not the design.