BeforeMerge

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

Product

  • Features
  • Explore
  • Pricing
  • Docs
  • GitHub

Company

  • About
  • Blog
  • Contributors
  • Contributing

Legal

  • Privacy Policy
  • Terms of Service
  • MIT License

© 2026 BeforeMerge. Built by Peter Krzyzek

BeforeMerge
Features
Explore
PricingBlogContributorsInstall Guide
3Sign In
FeaturesExplore
RulesSkillsKnowledgePrompts
PricingBlogContributorsInstall Guide
Sign In

Explore

Browse 354 rules, 42 knowledge articles, and 28 prompt templates across security, performance, architecture, and quality.

Sort:
Previous1...456...15Next

Automate these checks on every PR

BeforeMerge scans your pull requests against these rules automatically. Get actionable feedback before code ships to production.

Join WaitlistLearn More

354 rules

Defer or async non-critical scripts

MEDIUM

Load analytics, chat, and third-party scripts with defer/async so they never block rendering.

PerformanceWeb Performance

Preconnect to critical third-party origins

MEDIUM

Warm up DNS/TLS for required cross-origin hosts early with preconnect or dns-prefetch.

PerformanceWeb Performance

Compress and cache static assets aggressively

MEDIUM

Serve hashed assets with long-lived immutable cache headers and enable Brotli/gzip compression.

PerformanceWeb Performance

Code-split and lazy-load non-critical JavaScript

MEDIUM

Dynamically import below-the-fold and rarely-used components so the initial bundle stays small.

PerformanceWeb Performance

Optimize font loading

MEDIUM

Self-host fonts, preload critical ones, and use font-display: swap to avoid invisible or shifting text.

PerformanceWeb Performance

Serve responsive, modern-format images

HIGH

Use the framework Image component with srcset and AVIF/WebP so each device downloads an appropriately sized, well-compressed image.

PerformanceWeb Performance

Improve INP by keeping the main thread free

HIGH

Break up long tasks and minimize hydration so the page responds quickly to clicks and taps.

PerformanceWeb Performance

Prevent Layout Shift (minimize CLS)

HIGH

Reserve space for images, ads, and dynamically injected content so the page does not jump while loading.

PerformanceWeb Performance

Optimize Largest Contentful Paint (LCP)

HIGH

Make the main hero image or text render fast by prioritizing and preloading the LCP resource.

PerformanceWeb Performance

Expose Name, Role, and Value for Custom Controls

HIGH

For all UI components, the name, role, state, and value must be programmatically determinable—use native elements or correct ARIA. (WCAG 2.1 SC 4.1.2)

Quality

Identify Input Errors Clearly

HIGH

When an input error is detected automatically, the erroring field must be identified and the error described in text. (WCAG 2.1 SC 3.3.1)

QualityAccessibility

Provide Labels or Instructions for Inputs

HIGH

Form inputs must have visible labels or instructions describing the expected input. (WCAG 2.1 SC 3.3.2)

QualityAccessibility

Set the Language of the Page

MEDIUM

The default human language of each page must be set programmatically via the `lang` attribute. (WCAG 2.1 SC 3.1.1)

QualityAccessibility

Give Each Page a Descriptive Title

MEDIUM

Every page must have a `<title>` that describes its topic or purpose. (WCAG 2.1 SC 2.4.2)

QualityAccessibility

Provide a Visible Focus Indicator

HIGH

Any keyboard-focusable element must have a clearly visible focus indicator. (WCAG 2.1 SC 2.4.7)

QualityAccessibility

Manage a Logical Focus Order

HIGH

Components must receive keyboard focus in an order that preserves meaning and operability. (WCAG 2.1 SC 2.4.3)

QualityAccessibility

Prevent Keyboard Traps

CRITICAL

Keyboard focus must never become trapped in a component; users must be able to move away using only the keyboard. (WCAG 2.1 SC 2.1.2)

QualityAccessibility

Ensure Non-Text Contrast of 3:1

MEDIUM

UI components (inputs, buttons, focus states) and meaningful graphics must have at least 3:1 contrast against adjacent colors. (WCAG 2.1 SC 1.4.11)

QualityAccessibility

Reflow Content at 320 CSS Pixels

MEDIUM

Content must reflow to a 320px-wide viewport (400% zoom) without requiring two-dimensional scrolling. (WCAG 2.1 SC 1.4.10)

QualityAccessibility

Support Text Resize to 200%

MEDIUM

Text must be resizable up to 200% without loss of content or functionality and without assistive technology. (WCAG 2.1 SC 1.4.4)

QualityAccessibility

Do Not Use Color as the Only Visual Cue

HIGH

Color must not be the only means of conveying information, indicating an action, or distinguishing a visual element. (WCAG 2.1 SC 1.4.1)

QualityAccessibility

Preserve a Meaningful Content Sequence

MEDIUM

When content order affects meaning, the DOM reading/navigation order must match the intended sequence. (WCAG 2.1 SC 1.3.2)

QualityAccessibility

Convey Information and Relationships Programmatically

HIGH

Structure and relationships conveyed visually (headings, lists, tables, form labels) must be available programmatically or in text. (WCAG 2.1 SC 1.3.1)

Quality

Provide Captions for Prerecorded Video

HIGH

All prerecorded audio in synchronized media (video) must have captions. This makes speech and important sounds available to users who are deaf or hard of hearing. (WCAG 2.1 SC 1.2.2)

Quality
Accessibility
Accessibility
Accessibility