After evaluating dozens of pull requests, the author settled on a rule: leave only constructive comments—nitpicks, suggestions, questions—and approve the PR simultaneously. The approach relies on trust in teammates and fast CI cycles, allowing changes to be merged without delaying approvals.

The method presumes a low‑configuration environment where linters, formatters, and type checkers reduce trivial noise. By tagging comments with labels like nitpick: or question:, the reviewer signals intent while keeping the review concise. This reduces friction for teams that frequently face merge bottlenecks.

For blocking feedback, the author recommends either a standalone comment or a comment that blocks approval. The decision hinges on issue severity and team norms. In practice, most feedback should be non‑blocking to keep the codebase moving.

Adopting this workflow can turn code reviews into quick coaching moments. By approving while commenting, reviewers demonstrate care for quality without stalling progress, leading to cleaner code and faster releases.