Review a pull request effectively

Create a comprehensive pull request review guide for a [Language] engineering team. Cover what to look for in a review: correctness of the logic, presence and quality of tests, naming clarity, potential security issues, and performance implications. Provide guidelines on constructive communication tone and how to distinguish a blocking change request from a non-blocking suggestion. Explain how to use GitHub review features effectively including suggested changes, required reviewer rules, and review resolution. Define criteria for when a PR should be approved as-is, approved with optional nits, or explicitly requested to change before merging.