CO
Code Review Patterns
Keeping pull requests small, focused, and rapidly reviewed
Details
Language / Topic
_UUniversal
Category
Project Management
Rules
balanced
Code Review Patterns
- Keep Pull Requests under 400 lines of code to ensure comprehensive reviews and prevent rubber-stamping.
- Make PRs single-purpose. Do not mix refactoring changes with new feature additions in the same review.
Code Review Patterns
- Restrict Pull Request size strictly to <400 LoC. Smaller PRs receive faster, higher-quality reviews and are significantly easier to revert if bugs are discovered.
- Enforce the Single Responsibility Principle for PRs: a PR should do exactly one thing (add a feature, fix a bug, or refactor). Separate formatting/linting changes from logic changes.
- Provide clear context for the reviewer: include a descriptive summary, "how to test" instructions, and link relevant tracking tickets.