How do you handle code review and maintain quality standards in a PHP team?

Split it into what machines enforce and what humans discuss — the distinction is the point.

Automated, in CI:

• PHP-CS-Fixer or PHP_CodeSniffer against PSR-12, so formatting is never a review comment.
• PHPStan or Psalm at a level the team agrees, raised over time. Static analysis catches a large class of bug in a dynamically typed language.
• PHPUnit with the suite required to pass before merge.

Human review then focuses on what tools cannot judge: whether the approach fits the system, whether edge cases are handled, whether the naming will make sense in a year, and whether there is a security implication.

How to give review well: mark clearly which comments block the merge and which are suggestions; ask questions where you might lack context; keep pull requests small enough to actually read.

Note: If you have introduced any of this to a team that lacked it, lead with that. Raising a PHPStan level from 0 to 5 across a codebase is a concrete, credible achievement.