We kept shipping bugs that passed PR + CI — so we built something to stop it
For a while, we thought our process was solid: - PR review ✅ - CI passing ✅ - tests green ✅ And still… things were breaking in production. Not obvious bugs. More like: - edge cases in async flows - assumptions that didn’t hold under real load - logic that “looked correct” but wasn’t safe The frustrating part: nothing technically failed during review or CI. So everything felt safe — until it...
Passing tests ≠ safe code
One thing we learned the hard way: Passing tests doesn’t mean your code is safe. We had a PR that: - had good test coverage - passed CI - looked well structured Still caused a production issue. Why? Tests only covered expected paths. The real failure came from an untested edge case. And during review, nothing looked suspicious. That’s the tricky part — you’re not reviewing what’s missing. After...
We tried blocking bad PRs with AI before merge — here’s what actually worked (and what failed)
We kept running into the same annoying issue: PR looks clean Review is done Tests pass → merge → something breaks in production anyway After a few of these, it stopped feeling like “edge cases” and more like a gap in the process. So I started building something to sit right before merge and basically ask: “are we really safe to ship this?” Right now it: - looks at PR changes (not just test...
Building fast, scalable products that people actually use
Hey Product Hunt 👋 I’m Tareq — a Senior Software Engineer turned product builder. Over the last 10+ years, I’ve been obsessed with one thing: building fast, scalable products that people actually use. Recently, I stopped just shipping features for companies… and started building my own products from scratch. Here are a few things I’ve been working on: ⚡ SSHDeck — a secure SSH & SFTP desktop...



