Human-in-the-loop code review

    Human-in-the-loop code review means an AI model drafts the review comments and a person decides which ones are worth posting. GitReviewed works this way by default. It reads the diff, writes inline comments, and then waits. Nothing reaches the pull request until you approve it.

    How the review flow works

    1. Paste a pull request or merge request URL. GitReviewed fetches the diff for that request. There is no app to install and no CI job to configure.
    2. The model drafts inline comments. It reads every changed file and flags bugs, anti-patterns and security issues, anchored to the lines they refer to.
    3. You accept, edit or reject each comment. Keep the ones that are right, rewrite the ones that need your context, discard the rest.
    4. Approved comments post to the pull request from your own GitHub or GitLab account.

    Why comments post from your account, not a bot

    Review comments carry responsibility. When a suggestion turns out to be wrong, your teammates need to know who to ask about it, and a bot account cannot answer that. Posting from your account keeps the review attributable to a person who read it and agreed with it.

    It also means your teammates read one voice instead of two. There is no separate bot thread to triage alongside the human review.

    What the model looks for

    The draft comments cover bugs and logic errors, anti-patterns, and security issues in the changed lines. It works across JavaScript, TypeScript, Python, Go, Java, C#, Ruby, PHP, Rust and other major languages, on GitHub and GitLab, in public and private repositories.

    What you can control

    On the Pro plan you can set the review tone to formal or friendly, or describe the style you want in your own words, and set how many comments a review should produce. A light review on a small refactor and a thorough review on a migration are different jobs, and the depth setting reflects that.

    What this does not do

    It does not approve or merge anything. It does not comment automatically when a pull request opens, and it does not post without you. If you never open the review, nothing happens.

    It is also not a replacement for reading code you are responsible for. The reading gets faster because the first pass arrives already annotated. The judgment is still yours.

    Paste a pull request link and see the drafted comments before you decide on any of them. Three reviews a month are free.

    Review a pull request free