Your team agrees on something in Slack. Two weeks later a PR quietly breaks it. Nobody catches it until QA — or after deploy. Mo watches a Slack channel for decisions. When someone tags @mo to approve something, it stores it. When a PR opens, Mo checks the diff against every approved decision and flags conflicts before merge. It doesn't review code quality. It only cares if the code matches what the team actually decided.
We built this after it happened to us — a decision made in Slack
didn't make it into the code, and nobody caught it until a customer
hit it in production.
The frustrating part wasn't the bug. It was that the decision was
right there in #product-decisions. The PR just never got checked
against it.
Mo is the connection that was missing. Happy to answer any questions
about how the decision matching works under the hood.
The @mo to approve mechanic is clever. Lightweight enough that teams might actually adopt it without resistance.
Interesting approach. Curious how this handles the agent pipeline - when an AI agent opens the PR, does it still catch conflicts with decisions made before the agent was involved? The drift window starts earlier than that.
How do you decide which Slack discussions actually become enforceable rules without creating noise?
About Mo on Product Hunt
“Checks PRs against decisions your team approved in Slack”
Mo launched on Product Hunt on April 8th, 2026 and earned 94 upvotes and 9 comments, placing #11 on the daily leaderboard. Your team agrees on something in Slack. Two weeks later a PR quietly breaks it. Nobody catches it until QA — or after deploy. Mo watches a Slack channel for decisions. When someone tags @mo to approve something, it stores it. When a PR opens, Mo checks the diff against every approved decision and flags conflicts before merge. It doesn't review code quality. It only cares if the code matches what the team actually decided.
Mo was featured in Slack (72.2k followers), Developer Tools (511.1k followers) and GitHub (41.2k followers) on Product Hunt. Together, these topics include over 86k products, making this a competitive space to launch in.
Who hunted Mo?
Mo was hunted by Oscar Caldera. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Mo stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Oscar Caldera