first the automated part, that makes a pr "review ready", this helps us alot to gain confidence. 1. Automated tests that actually test real cases 2. Automated

first the automated part, that makes a pr "review ready", this helps us alot to gain confidence. 1. Automated tests that actually test real cases 2. Automated tests to test for regressions 3. Automated end-to-end tests, to make sure all core functions (and new functions still work and ui flows are stable / correct) 4. automated ai reviews (we use strix for security and a small Copilot SDK harness) 5. linters (for go: gosec,govuln) and formatters For the human review process, we try to "never do big refactorings out of the blue", normally we do this in pair, or in tight loops. We dont have special reviewer roles, every dev can review any pr, we think, that everyone in a team is responsible for the product (and its quality, this also helps alot with knowledge transfare, we have retros and dojos to keep everyone on the same levle and align our teams "taste").