Mo – checks GitHub PRs against decisions approved in Slack
Slack-to-PR decision tracking, but landing page shows a different product entirely.

Slack-to-PR decision tracking, but landing page shows a different product entirely.
Software agencies and dev teams using Slack + GitHub
Linear · Jira · Slack bots
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 the approved decisions and flags conflicts before merge.
It doesn't review code quality. It only cares whether the code matches what the team actually agreed to.
Would love feedback, especially from anyone who's been burned by this exact problem.
Slack-to-PR decision tracking, but landing page shows a different product entirely.
Markdown ADRs automatically surface on PRs — prevents institutional amnesia at scale.
You can mention a bot in Slack or Discord and have it queue a job that clones an approved repo, runs a coding agent via the Codex/Copilot CLI, and posts a Markdown report or a PR link back in-thread — that conversational-to-PR flow is the project's strongest move. The architecture (bot → Redis queue → worker → agent → repo-scoped PRs) and repo catalog make it practical for teams who want to keep AI-driven edits auditable and self-hosted; just be mindful of the security model since the worker runs code against repos.
CODEOWNERS for architectural decisions—surfaces why code exists before breaking it.
Markdown-driven decision surfacing with Trie-based matching outperforms Slack threads.
Another code review tool claiming to catch slop, competing with CodeRabbit and Cursor.