Ask HN: How / What do you use for Code Review?
5 comments
there might be not much good enough solutions on the market yet that would substitute senior eng review
I am digging into this for some time and the main reason seems to be in definition of what good review is. Its less about finding bugs and more about code evolvability, maintainability and simplicity. without some context that would give a hint how the app will evolve over time, is maintained and what is simple/hard for live person - llm struggle to deliver useful insights here.
here you can find some related papers: https://github.com/sermakarevich/ai_knowledge_wiki/blob/mast...
I am digging into this for some time and the main reason seems to be in definition of what good review is. Its less about finding bugs and more about code evolvability, maintainability and simplicity. without some context that would give a hint how the app will evolve over time, is maintained and what is simple/hard for live person - llm struggle to deliver useful insights here.
here you can find some related papers: https://github.com/sermakarevich/ai_knowledge_wiki/blob/mast...
Agree, maybe we need to build something. It sounds like a good use case. Claude has a /pr-review that sometimes does a good job, but it's not consistent.
A while back I used Gerrit for reviewing changes to infrastructure automation, not sure if that counts.
What are you guys using for code review?
Obviously Codex / Claude GitHub connectors are not doing a good job and paying per use for Code Rabbit is rediculous expensive.