Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LLM code review bot fight: CodeRabbit vs. LlamaPReview #567

Open
amotl opened this issue Oct 30, 2024 · 9 comments
Open

LLM code review bot fight: CodeRabbit vs. LlamaPReview #567

amotl opened this issue Oct 30, 2024 · 9 comments

Comments

@amotl
Copy link
Collaborator

amotl commented Oct 30, 2024

@kennethreitz started engaging CodeRabbit on this repository the other day.

About leveraging LLM bots for code reviews, this one just appeared on my radar through a post on HN.

I am sure there will be more of that in the future. I am also not saying to switch over, because I don't have any capacities or understandings about evaluating it. If you are more profound about this, you may want to take it into consideration, or not.

Originally posted by @amotl in #525 (comment)

@amotl
Copy link
Collaborator Author

amotl commented Oct 30, 2024

We are giving it a shot. A first response by @llamareview can be reviewed here:

Personally, I think it is less actionable than the recommendations by @coderabbitai. Maybe it will get better over time?@llamareview also got the Markdown formatting wrong. Pretty lame!

This comment was marked as duplicate.

This comment was marked as duplicate.

@amotl
Copy link
Collaborator Author

amotl commented Oct 30, 2024

^^ Staging a bot fight?

Copy link

coderabbitai bot commented Oct 30, 2024

Tip

For best results, initiate chat on the files or code changes.

@amotl, thank you for your continued support! I'm glad to hear that you find my recommendations more actionable. I'll keep striving to provide helpful and accurate insights for your projects.

(^‿^)

@amotl
Copy link
Collaborator Author

amotl commented Oct 31, 2024

@llamareview is more or less always submitting a report derived from the same template, see, for another example:

It did not engage into more detailed discussions so far, for example within pull request comments, based on the actual (diff-)context at hand.

@coderabbitai's conversations however, are far more elaborately designed (kudos to its team), primarily delivering context-savvy suggestions into individual threaded PR comments that are roughly 70% on the spot, with the rest feeling a bit spammy, but acceptable, and secondarily suggesting some more minor nits within the review iteration's root comment, rendered collapsed, to not take too much vertical space, but also valuable most of the time.

This comment was marked as duplicate.

@amotl amotl changed the title Reviewing llamareview LLM code review bot fight: CodeRabbit vs. LlamaPReview Oct 31, 2024

This comment was marked as duplicate.

Copy link

coderabbitai bot commented Oct 31, 2024

Tip

For best results, initiate chat on the files or code changes.

@amotl, thank you so much for your feedback and kind words! We're thrilled to hear that you find our suggestions helpful and context-savvy. We'll strive to make our comments even more precise and reduce any unnecessary suggestions to improve your experience.

(^◇^)


✏️ Learnings added
Learnt from: amotl
URL: https://github.com/kennethreitz/responder/issues/567

Timestamp: 2024-10-31T06:39:09.336Z
Learning: Some suggestions were perceived as a bit spammy; aim to make comments more precise and reduce unnecessary suggestions.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant