Show HN: I built a tool to review my teammates' pull requests faster
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!
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!
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