BeforeMerge
FeaturesExploreSkillsPricingBlogDocs
Sign In
FeaturesExploreSkillsPricingBlogDocs
Sign In
BeforeMerge

AI-native code review knowledge base. Structured rules that catch what linters miss.

Product

  • Features
  • Explore
  • Pricing
  • Docs
  • GitHub

Company

  • About
  • Blog
  • Contributing

Legal

  • Privacy Policy
  • Terms of Service
  • MIT License

© 2026 BeforeMerge. Built by Peter Krzyzek

  1. Blog
  2. Introducing BeforeMerge
AnnouncementMarch 5, 2026

Introducing BeforeMerge

An AI-native code review knowledge base with structured rules that catch what linters miss. Open source, MIT licensed.

Share

What is BeforeMerge?

BeforeMerge is an AI-native code review knowledge base — a structured collection of rules organized into skills that teach AI reviewers (and humans) what to look for in pull requests.

Unlike traditional linters that focus on syntax and formatting, BeforeMerge rules encode architectural decisions, security best practices, and framework-specific patterns that are typically only caught by senior engineers during manual review.

Why We Built This

Every team has unwritten rules. Things like:

  • "Always enable RLS on new Supabase tables"
  • "Never use getServerSideProps for static content in Next.js"
  • "WordPress hooks should use a namespace prefix"

These rules live in engineers' heads. They get shared in PR comments, forgotten in onboarding docs, and inconsistently enforced. Senior engineers spend hours repeating the same feedback.

We wanted to create a single source of truth — a knowledge base that's structured enough for AI to consume, but clear enough for any developer to learn from.

How It Works

Skills

A skill is a collection of related rules for a specific technology. For example, the supabase-nextjs skill contains rules about Row Level Security, edge function patterns, auth handling, and more.

Rules

Each rule is a structured document with:

  • Impact level — CRITICAL, HIGH, MEDIUM, or LOW
  • Section — which part of the stack it covers (security, performance, architecture)
  • Body — detailed explanation with code examples
  • Detection patterns — grep and semgrep patterns for automated detection
  • CWE/OWASP mappings — links to recognized security standards

Integration

Rules are designed to work with AI code review tools. Pipe them into your review workflow, and your AI reviewer gains the collective knowledge of experienced engineers.

Open Source

The entire knowledge base is MIT licensed. We believe code review knowledge should be shared, not locked behind proprietary walls.

You can:

  • Browse all rules at /explore
  • Contribute new rules and skills via GitHub
  • Use the rules in your own tools and workflows

What's Next

We're building an automated PR review service that applies these rules to your pull requests on every push. Join the waitlist to get early access.

In the meantime, explore the rules, star the repo, and let us know what skills you'd like to see next.

launchopen-sourcecode-review

On this page

  • What is BeforeMerge?
  • Why We Built This
  • How It Works
  • Skills
  • Rules
  • Integration
  • Open Source
  • What's Next