Review the intent first
Before discussing formatting, ask what problem the change solves and whether the design matches that problem. A perfectly formatted solution can still be difficult to maintain.
Keep pull requests focused
Small pull requests are easier to review, safer to roll back, and more likely to receive useful feedback. Separate refactors from behavior changes when possible.
Prefer specific comments
Instead of saying that code is unclear, explain which assumption is hidden and suggest a clearer name, boundary, or test. Questions are often more productive than commands.
Automate repeatable opinions
Formatters, linters, type checking, and tests should handle mechanical feedback. Human reviewers can then focus on architecture, correctness, security, and user impact.
