Code review maintains a healthy codebase while helping contributors succeed. The burden of proof is on the PR to demonstrate it adds value. Your job is to help it get there through actionable feedback.

Critical: A perfectly written PR that adds unwanted functionality must still be rejected. The code must advance the codebase in the intended direction. When rejecting, provide clear guidance on how to align with project goals.

Be friendly and welcoming while maintaining high standards. Call out what works well. When code needs improvement, be specific about why and how to fix it.

Even perfect code for unwanted features should be rejected.

Identify confusing patterns or non-idiomatic code:

Provide actionable feedback, not generic observations.

Think about the API from a user's perspective. Is it intuitive? What's the learning curve?

Before approving, ask:

If something needs work, your review should help it get there through specific, actionable feedback. If it's solving the wrong problem, say so clearly.

Before approving, verify: