Show HN: I built a tool to review my teammates' pull requests faster

1•edai-•1d ago

Hi HN,

I’m Valentin, a developer who’s found code reviews to be a slow process, especially after context switching or juggling different projects and languages. Even reviewing my own code can be tough when I’ve lost the thread or just need a fresh perspective.

Over the past few weekends, I built GitReviewed to make PR reviews faster, smarter, and genuinely useful for real teams.

What it does:

- Reviews any GitHub or GitLab pull/merge request with AI-powered comments, spotting security issues, code patterns, typos, and more

- Posts comments as you (not a bot), so feedback fits naturally into your workflow

- Lets you tweak the feedback’s tone and detail level to match your team’s style

- Neat trick: Just swap github.com or gitlab.com for gitreviewed.com in any PR/MR URL to jump straight to an instant review

This is my first SaaS project, so I’d really appreciate any feedback, suggestions, or advice from anyone who’s been down this road.

I’ll be around in the comments! Thanks for checking it out!

Comments

fjfaase•1d ago

Code reviews take a lot of time and delay intergration. As an alternative, you could do away with them to just do all commits on a single branch. That is the ultimate form of Continuous Intergration. As a developer you can do work on your own 'private' branch before merging to the main branch and having a tool to review your own code changes would be usefull.

edai-•1d ago

Appreciate the comment! You’re right, merging straight to main works for some teams. But in companies I’ve worked at, peer review is required and the process can definitely slow things down (whether it’s policy or just the team culture).

That’s actually one of the idea behind this tool: helping you review your own code before merging. In fact, I used it to review my own code while building this project

pin-yi•1d ago

This is super useful—well done! Code reviews can easily become a bottleneck, especially when juggling multiple projects or switching contexts. I really like your approach of using AI to generate human-like comments—it feels like a natural part of the workflow rather than an interruption.

edai-•1d ago

Thank you, I really appreciate the kind words!

mmarian•1d ago

What's the benefit of using this vs GitHub's own PR copilot? Also, I think you'll struggle with the pricing structure - too low for individual devs to bother using. And no larger companies will be open to let you access their private repos, so you have to cater to individuals at first (or open source).

edai-•13h ago

Great questions, thanks for the thoughtful feedback!

On Copilot PR reviews: GitReviewed works for both GitHub and GitLab (with plans to add Bitbucket and Azure DevOps), and lets you fully customize the review tone and style. Comments are posted as you, not a bot, so reviews feel natural and human. The goal is to make reviews faster and more helpful for real workflows. I believe peer reviews will still be around for a time.

Pricing: Finding the right price point is definitely a challenge for me. I wanted to keep it accessible for individuals and small teams, but I’m open to adjusting the structure as I get more feedback.

On company trust: Absolutely, larger companies have mentioned being cautious with new SaaS tools like mine. For now, I’m focusing on individual devs and keeping things as transparent as possible regarding permissions and data.

GitReviewed works with your own PAT (for GitHub), GitHub OAuth or GitLab OAuth, so it only accesses what you can see - no extra permissions required. You can review PRs as if you were doing it yourself on their UI, without granting full repo access. Only GitHub OAuth (not PAT) requests broader permissions, while I give the choice to the user to keep this way or PAT way.

Thanks again, this kind of feedback is super helpful as I keep improving things!

Economics and labor rights in AI skepticism

Meta Signs Nuclear Power Deal to Fuel Its AI Ambitions

The HTTP Query Method

AI LLMs can't count lines in a file

What do software developers need to know to succeed in an age of AI?

Show HN: AI Email Prioritizer – Auto-Organize Gmail with Nvidia LLM

Hacksaw: Hardware-Centric Kernel Debloating (2023) [pdf]

Mikko Hypponen Leaves Anti-Malware Industry to Fight Against Drones

Subtxt/Dramatica

Show HN: Code Search Mcp for GitHub

How pets alter your immune system

Florida ban on kids using social media likely unconstitutional, judge rules

The End-of-History Illusion

Show HN: CrowdRender – collaborative rendering plugin for Blender

Show HN: Hashish v5.5.1 – C++ Hash Cracker, Extreme Performance Boost

Tim Sweeney Didn't Expect a Five-Year Fortnite Ban

The OpenAI Board Drama Is Turning into a Movie

Show HN: Certificate transparency log with LSM-tree based storage

Qt's New Bridging Technology – Looking Back to Move Forward

Where's Marty McFly's guitar? Search for Back to the Future prop 4 decades later

Chocolate-quake: A purist Quake source port

IAS Interview with Demis Hassabis on the Future of Knowledge [video]

Cook My Meat

June of Stories: Read a Short Story Every Day in June

If This, Then That, Except for When

Things are different between system and application monitoring

Aurora DSQL: How to spend a dollar

Meta pauses mobile port tracking tech on Android after researchers cry foul

American Malware

How China Uses Work to Reshape Uyghur Identity and Control a Strategic Region