I was spending 2 hours a day reviewing PRs. Then I found this tool.
Let me be honest. I used to spend a significant chunk of my day reviewing pull requests. Not the interesting parts — not the architecture decisions or the tricky business logic. The repetitive part...

Source: DEV Community
Let me be honest. I used to spend a significant chunk of my day reviewing pull requests. Not the interesting parts — not the architecture decisions or the tricky business logic. The repetitive parts. The same comments, over and over, on every PR: "You forgot @Valid on this @RequestBody" "Don't inject the repository directly into the controller, use a service" "This catch (Exception e) has no logging — how are we supposed to debug this in production?" "This service method writes to the database but has no @Transactional" Every. Single. PR. I knew these rules by heart. My team knew these rules by heart. And yet, every week, the same issues kept slipping in. Because humans get tired. Humans miss things. And nobody wants to be that reviewer who leaves 15 comments on a junior developer's first PR. I started looking for a solution I tried a few generic linting tools. They caught style issues and basic syntax problems, but nothing Spring Boot specific. Nothing that understood the patterns we