Tomosu AI

Tomosu AI

Production Reliability Governance

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Recently Supported

Tomosu
Tomosu AI Production Reliability Governance, Powered by PRI.

Forums

•

1mo ago

We got tired of reading AI review comments that didn't stop prod from breaking, so we built Tomosu.

Hi everyone

Our PRs were going through AI code review like everyone else's. Every PR came back with a long list of comments: naming, style, a missing null check, "consider extracting this function". We read all of it, fixed what made sense, and merged.

Then some of those reviewed, approved, "looks good" changes still broke in production.

The review wasn't wrong. It just answered a different question. It told us whether the code looked right. It never told us whether this change, in this part of the codebase, would hold up once it shipped.

What do you check before putting a vibe-coded app in front of real users?

Genuine question for people shipping with Lovable, Bolt, v0 or Cursor. Building fast is the whole point, but the same few problems keep showing up on freshly shipped apps when you look at them from the outside: admin or debug routes left reachable, API endpoints that return another user's data if you change an ID in the URL, Supabase or Firebase tables readable without logging in, and API keys sitting in the frontend JavaScript. None of these need a hacker to find, just someone curious with a browser. So how do you handle it? Do you have a checklist before launch, rely on the platform's defaults, ask the AI to review its own code, or ship and fix later? And which of these has actually bitten you? Disclosure: I work on external recon at Xseth, so this is my day job, but I'd really like to hear what works for people here, with or without tools.

•

3mo ago

Does your AI reviewer ever tell you it does not know?

I asked an AI assistant to review a repo before shipping it.

It came back with a clean report, a confident tone, and a long list of passes. Then I checked one of the lines it cited.

The line said something else. The mistake itself didn't bother me that much. What bothered me was that there was no shape in the output for "I don't know."

Everything was either a problem or a pass. And the passes were doing a lot of unearned work.

View more