PullMatch

Why PullMatch

GitHub shows the diff.PullMatch shows what matters.

Standard review asks everyone to parse implementation details. PullMatch turns the same pull request into a readable decision a founder, PM, or operator can actually make.

Standard Review (GitHub)

Dense diff chaos

Implementation overload

dashboard/middleware.ts

@@ -118,17 +145,34 @@
- const isAllowed = hasFeatureFlag(user, "beta-dashboard");
- if (!isAllowed) return redirect("/waitlist");
+ const invite = await getInviteByEmail(session.user.email);
+ const isAllowed = invite?.status === "approved";
+ if (!isAllowed && pathname.startsWith("/dashboard")) {
+ auditLogger.info("blocked-dashboard-access", { userId, pathname });
+ return redirect(`/beta-gate?next=${pathname}`);
+ }
@@ -201,8 +246,19 @@
- analytics.identify(user.id);
+ analytics.identify(user.id, { betaGate: invite?.status ?? "none" });
+ metrics.increment("beta_gate.checked");

Readable Review (PullMatch)

Swipe card clarity

Business-first context
Medium risk6 files changed

Add invite-only beta gate to dashboard routes

AI summary

This change keeps unfinished dashboard screens private. It blocks non-invited users and logs attempted access, so the main risk is whether the allowlist logic accidentally locks out a valid customer.

Why a non-engineer can review this

The question is not “is the middleware elegant?” It is “does this safely hide unfinished product work from the wrong people?”

Approve, reject, keep the receiptPowered by Permission Protocol
Review speed
2 hours
4 seconds
Audience
Engineers only
The whole team (Founders, Ops, PMs)
Context
Implementation details
Business risk
Mobile
Desktop only
Mobile-first (Swipe from the back of an Uber)
Accountability
Hidden approvals
Immutable receipts

Make Review Obvious

Stop asking the whole team to read diffs. Show them the decision instead.

Open the demo, swipe through the flow, then get on the waitlist before your next AI-assisted merge ships without a readable review.