|
|
|
|
|
|
by kostas_f
420 days ago
|
|
|
Congrats on the launch! I’ve tried several AI code reviewers in the past few months and honestly, most of them fall short in the same ways - they lack proper context about the codebase and can’t remember discussions from previous PRs or design decisions. IMO the tools that will win this space will be the ones that properly understand the codebase context and coding/architecture patterns. Btw are you also planning to support customizable rules for code reviews? |
|
|
Also, there is context that’s not just code but documentation/guidelines etc, plenty of experimentation to be done there.
Customisable rules? YES - i ve got a lot of plans currently on this. I see two layers of customisation: - allow the user to customise when and how often reviews happen, and how they re triggered (i.e every commit/every x mins etc, avoid running prs on specific files I.e package.json changes etc) - pass in custom rules to the reviewer that work well for you(or team in the future). This will allow the tool to be more dynamic in nature as opposed to just LLM + your code.
Hope this answers your questions, thank you for the support!