Mo Check installs statistics

Mo connects Slack and GitHub to ensure pull requests follow approved decisions. It captures decisions made in Slack and checks PRs against them, flagging conflicts before merge. Teams catch mismatches early, avoid costly mistakes, and keep code aligned with what was agreed without changing their workflow.

Capabilities

• Flags pull requests when the diff conflicts with decisions your team approved in Slack (recorded in your normal workflow). • Runs automatically on PRs for repositories you select—while the PR is open, before merge. • No repo config files or code changes required for the standard setup. • Complements human review by focusing on decision alignment (what was agreed) rather than generic style-only feedback.

Benefits

• Ship what was approved: Catch changes that contradict what the team captured in Slack before they reach main. • Early, actionable signal: Feedback shows up on the PR so you fix drift during review. • Fits your stack: Keeps Slack as the source of approvals and GitHub as the source of truth for code—Mo connects them.

Getting Started

Requirements

• Slack: Workspace admin/install permissions to add the Mo app (start from /mo → Start with Slack). • GitHub: Permission to authorize Mo and grant access to the repos you want checked (Connect GitHub in the Mo portal). • Plan: Trial and billing are shown in the Mo app after signup.

Setup

• Open the Mo web app at /mo, choose Start with Slack, and finish Slack’s Allow screen. • In the Mo portal, use Connect GitHub and pick the repositories Mo should watch. • Continue deciding in Slack as you do today; open or update a pull request—Mo checks the diff against approved decisions and surfaces conflicts on the PR.

Example Prompts

Try these prompts with @mo:

• "Does this pull request conflict with what we approved in Slack for this feature?" • "Summarize the Mo check on my open PR and which decision it is comparing against." • "What approved decisions would Mo use when checking this branch?" • "Does this diff align with our recorded scope for exports (or billing, trials, etc.)?" • "Explain why Mo might fail a check here before I merge."

Description from the GitHub Marketplace listing.