[austin-cheney]

Then, yes, if the risk is largely off loaded to automation tasks then larger PRs become far more reasonable. Reviews file by file does not lower complexity, but just segments your effort so as to allow the task to become less daunting. Since you do have good automation in place perhaps the most important thing to review during your PRs is organizational complexity, which appears to be your primary concern. If the change requires tremendous effort due to organization concerns that might be a strong point for push back and refactor such that like conventions are grouped together to lower complexity into the future. Although refactors like this increase effort in the immediacy they lower tech debt at future maintenance. Another benefit of strong automation already in place is that large scale refactors are low cost efforts.