GitReviewed
    Back

    Roadmap for GitReviewed

    Last updated: 2026-08-20

    Welcome, and thanks for your interest in GitReviewed!

    I'm Valentin, the founder and developer behind GitReviewed. I built this tool to help developers (myself included) write better pull request reviews, faster, and with less mental fatigue.

    Here's where things stand: what works today, what I'm building at the moment, and what I haven't decided on yet.

    ✅ Live today

    • GitHub and GitLab, on public and private repos
    • An optional Personal Access Token, so you can post comments without waiting on an org admin
    • Accept, edit, or reject each suggestion. Nothing reaches your PR unless you approve it
    • Comments posted from your own account, not from a bot
    • Light, balanced or thorough review depth, friendly, formal or playful tone, and custom prompts on Pro
    • A side-by-side diff viewer, with comments sitting next to the code they're about

    🚧 Working on now

    Large pull requests. Big diffs get cut short today. I'm sorting files by how much actually changed in them and splitting the review across several passes, so a 40-file PR gets read instead of truncated.

    Shorter comments. Some reviews come back wordier than they need to be. I'm tightening the prompts, and adding a "shorten" button for the ones that still run long.

    Accept All and Reject All. When a PR comes back with twenty comments, clicking through them one at a time gets old.

    Replies. Answering review threads on GitHub and GitLab without leaving GitReviewed.

    🔭 Exploring

    No promises on these. Whether they get built, and in what order, depends on what people ask for:

    • Bitbucket and Azure DevOps
    • A VS Code extension, so you don't have to leave your editor
    • Picking your own model, or bringing your own API key

    Security and compliance

    Today: diffs are processed in memory and never stored, access tokens are encrypted with AES-256, and everything travels over TLS.

    Formal certification is a separate question. SOC 2 Type II, third-party penetration tests, and audited compliance programs cost real money for a one-person team, so I'll pursue them when enterprise demand pays for them. I'd rather tell you where I stand than show you a badge I don't have. If your company needs a specific attestation before it can use GitReviewed, email me and say which one. That's what moves it up the list.

    What GitReviewed does with your data today is written up in the Privacy Policy.

    Bugs, ideas, or just a "hey, this is cool": all of it helps.

    📬 support@gitreviewed.com You can also vote on features and leave ideas on Insighto.

    Thanks for being part of this,

    — Valentin