Drowning in Nitpicks: Why I built a noise filter for my PRs

by allenz

Review fatigue is real.
I recently opened a PR for a small feature. Reviewing it with a generic AI tool gave me 40 comments.
35 of them were about variable naming preferences or "best practices" that didn't apply to our specific architecture.
The other 5 were actually useful, but I almost missed them because I was so annoyed by the first 35.

It feels like we've replaced "waiting for a senior dev" with "arguing with a robot about indentation".
The whole point of automation was to save time, not to turn us into prompt janitors.

I just wanted something that shuts up about the small stuff and screams about the big stuff (Security, Performance, Logic).
I couldn't find it, so I built a tool to solve it.

I hacked together CodeProt to focus purely on high-signal issues. It uses AST analysis to filter out the noise and only flags things that actually matter. It's not perfect, but it's finally quiet enough that I can actually think.

If you're burning out on review noise, maybe it helps you too.