Skip to content
QualityMaxQualityMaxQualityMax Docs

Code Review & Gates

Every pull request on a connected repository runs through the QualityMax review pipeline: four independent gates that run in order, each producing its own verdict. On top of the pipeline, Nexus provides multi-persona AI review inside the app, and the code-health scan posts line-level findings straight to GitHub.

The four gates

Section titled “The four gates”
Gate What it does When it runs On failure
Alpha AI code-diff review + security (SAST) scan Always, on every PR WARN or hard block
Gamma Your repo’s native test suite (Go / Rust / pytest) If a supported framework is detected Hard block
Delta QualityMax-generated test scripts, matched to your framework If the project has matching scripts Soft warning
Beta Playwright tests against the preview deployment After a successful deploy webhook Hard block

Gates are independent and skippable — a repo with no Rust code simply never runs Gamma’s Rust path. The pipeline starts when the GitHub App webhook receives a push or pull_request event, and gates run in order: Alpha, Gamma, and Delta complete synchronously; Beta waits for your deploy provider (Vercel, Railway, and others) to report a live preview URL.

How the final verdict is computed

Section titled “How the final verdict is computed”
gate_conclusion starts as "success"
    Alpha WARN  → action_required
    Alpha BLOCK → failure
    Gamma fail  → failure (hard override)
    Gamma pass  → reverts an earlier WARN back to success
    Delta fail  → action_required (only if currently "success")
    Beta fail   → failure

A green check never hides a red gate: the strictest verdict wins. The one deliberate exception is Delta — AI-generated tests can have false positives, so Delta downgrades failures to warnings and never blocks a merge by itself.

Configuring gates

Section titled “Configuring gates”
  • Disable Gamma + Delta per project: turn off test execution in the project’s Test Framework settings.
  • Disable Beta for a repo: mark the repository as a non-web app type (CLI tool, TUI agent, library/SDK, docs site, or API-only) — non-web repos have no preview deployment.
  • Add Delta coverage: create automation scripts for the project (via the UI or MCP add_script_to_framework). Existing scripts automatically become Delta checks on future PRs.

In this section

Section titled “In this section”