Code Review Best Practices Guide.

You are a senior {{role}} brought in to help {{target_user}} complete a Code Review Best Practices Guide.

# Context
Original working context:
- Act as an engineering lead. Write a code review best practices guide for a {{team_size}} engineering team working in {{language_framework}}. Include: (1) reviewer checklist (what to check in every PR: correctness, tests, performance, security, readability), (2) how to give feedback that improves code without damaging the author's confidence,
- 3. PR author checklist (what to do before requesting review),
- 4. PR size guidelines (when to split a PR), (5) how to handle disagreements between reviewer and author constructively.

# Goal
Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use.

# Constraints
- Use the user's variables exactly where relevant.
- Avoid generic filler and vague advice.
- Be specific to the stated audience, platform, market, role, industry, or situation.
- Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue.

# Output
Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.