Content

Bad code review trend #1: The “Just merge it” mentality
Bad code review trend #2: “Code reviews are for juniors”
Bad code review trend #3: “Nitpicks are toxic”
Bad code review trend #4: Frequently turning code reviews into a performance (aka the live review trap)
Bad code review trend #5: Not reading through your AI-code first
Code review etiquette: How to be a code reviewer people want to work with

Back to blog

Good code review advice doesn't come from threads with 🚀 in them

by Emily Lint

July 16, 2025

8 min read

Cut code review time & bugs by 50%

Most installed AI app on GitHub and GitLab

Free 14-day trial

Get Started

Cut code review time & bugs by 50%

Most installed AI app on GitHub and GitLab

Free 14-day trial

Get Started

Keep reading

July 16, 2025

Good code review advice doesn't come from threads with 🚀 in them

Bad code review trends you should definitely not follow

July 08, 2025

What percentage of your code should be AI-generated?

We’ll come clean: That title is mostly clickbait. This isn’t an article where we tell you that 20% or 30% or even 50% of your codebase should be AI-generated. We’re writing this because it’s looking like very soon someone could be telling you that. ...

July 02, 2025

Code Guidelines: Bring your coding rules to CodeRabbit

Coding Guidelines automatically scans .cursorrules, .copilot-instructions, and other coding standards as part of our context enrichment process.

Still have questions?

Content

Good code review advice doesn't come from threads with 🚀 in them

Share

Cut code review time & bugs by 50%

Share

Cut code review time & bugs by 50%

Keep reading

Good code review advice doesn't come from threads with 🚀 in them

What percentage of your code should be AI-generated?

Code Guidelines: Bring your coding rules to CodeRabbit