Code Review Guidelines for Effective Collaboration

Code reviews improve code quality and share knowledge across the team.

For Authors#

Before Requesting Review#

• Self-review the diff first
• Ensure tests pass
• Write clear PR description
• Keep PRs focused and small (<400 lines)

Good PR Description#

For Reviewers#

Comment Types#

Constructive Feedback#

Review Checklist#

• Does it solve the problem?
• Is it tested?
• Is error handling appropriate?
• Any security concerns?

Focus on important issues, be constructive, and remember reviews are about shipping better software together.