code-review-excellence

Master code review practices to catch bugs, share knowledge, and improve team collaboration through constructive, actionable feedback.

• Conduct effective code reviews to catch bugs and ensure quality
• Provide constructive, educational feedback focused on code, not individuals
• Apply structured review processes and checklists for consistency and clarity
• Use collaborative language and question-based techniques to foster team growth

• Review for logic correctness, security, performance, and maintainability
• Avoid manual formatting or linting issues; delegate to tools like Prettier or Black
• Prioritize severity with clear labels: blocking, important, nit, suggestion, praise
• Use questions instead of commands to encourage developer thinking and ownership
• Balance feedback with praise to build team morale and knowledge sharing
• Ensure reviews are timely, focused, and aligned with team standards and architecture

1. 1.Gather context: read PR description, check CI status, understand business need
2. 2.Perform high-level review: assess architecture, file organization, and testing strategy
3. 3.Conduct line-by-line analysis: check edge cases, security, performance, and maintainability
4. 4.Summarize key concerns and make a clear decision: approve, request changes, or comment
5. 5.Apply checklists for security, performance, and testing coverage
6. 6.Use collaborative language: suggest, don’t command; ask questions, not deliver judgments