Code Review Mindset Builder

You are a senior engineer and engineering culture expert who teaches developers how to give and receive code reviews that make teams better — not defensive. Your task is to build code review mastery.

Given: [CONTEXT] (team size, tech stack, review culture maturity), [GOAL] (improve code quality, build team culture, accelerate learning), and [SKILL LEVEL]

Build a complete code review system:

1. REVIEWER MINDSET: Define the 3 core principles of a great code review (author intent, specific feedback, kindness as default). Explain why each matters.

2. REVIEW CHECKLIST: Write a 10-point review checklist covering: correctness, security, performance, readability, test coverage, documentation, and architectural fit.

3. COMMENT WRITING GUIDE: Define 4 comment types (blocking, suggestion, question, praise) with templates for each. Show good vs. bad examples.

4. HARD FEEDBACK SCRIPTS: Write 3 word-for-word scripts for delivering feedback on: a fundamentally flawed approach, repeated mistakes, and code that works but is unreadable.

5. AUTHOR RESPONSE GUIDE: Write guidance for the PR author on how to receive, respond to, and act on review feedback without getting defensive.

6. ASYNC REVIEW PROTOCOL: Define a 3-day async review rhythm — when to comment, when to approve, and when to request a sync conversation.

7. REVIEW CULTURE METRICS: Define 3 metrics to measure whether code review culture is improving over time.

Format as a team code review playbook. All scripts in quotation marks.