Mo checks pull requests against approved onboarding rules before merge. Required steps, review gates, confirmations, trial activation, and first-run flows — caught before they ship.
Approve onboarding rules in Slack. Mo checks the code before merge.
#onboarding-rules
@Mo approve this
"Users must confirm email before starting a trial."
Pull request #91
A required step gets skipped.
A confirmation screen disappears.
A user reaches trial access too early.
An approval gate is bypassed.
A first-run sequence no longer matches what product approved.
The product still loads. The flow still sort of works. But the onboarding experience is no longer the one the team agreed to ship.
Mo catches that before merge.
Keep mandatory steps in place, including email confirmation, account setup, profile completion, and approvals.
Catch pull requests that activate users too early or skip required checks.
Protect screens and checkpoints that should appear before activation, payment, or access.
Catch changes that affect role-based or plan-based onboarding paths.
Protect setup sequences, default states, and guidance the team intentionally designed.
Onboarding logic often spans frontend, backend, flags, and conditional checks. A pull request may pass review and still break the intended path. Traditional code review focuses on implementation. Mo focuses on whether the flow still follows the approved rule.
Checks if the implementation looks right.
Checks if the onboarding flow still matches what was approved.
That difference matters when the code works but the experience is wrong.
Protect trial activation rules, profile completion steps, and first-run setup.
Protect review gates, compliance checks, and manual approval requirements.
Protect different entry flows for admins, members, guests, partners, or operators.
Capture onboarding rules with @mo approve this in any Slack channel.
Mo watches pull requests in GitHub or GitLab automatically after connecting.
If the code changes the onboarding flow in a way that breaks the rule, Mo flags it before merge.
Teams can also upload onboarding specs or flow notes and approve the rules they want enforced.
Mo is best when teams approve clear onboarding rules that should be enforced before merge.
Yes. Teams use Mo to protect onboarding steps that must stay in place, including approval and verification gates.
No. Mo is designed to catch onboarding rule drift across the code paths that affect the final flow.
Used internally at Advante across 12+ projects including:




Approve onboarding rules in Slack. Let Mo catch flow drift before it ships.
PR enables: trial before confirmation