build-quality-gates

To enforce a multi-stage build pipeline, use sequential gate validation to verify compilation, linting, type checking, and bundling pass before deployment. This pre-deploy check catches structural and packaging regressions by requiring each gate to pass before proceeding.

The best way to run pre-PR build checks is using platform detection to infer build commands for common systems like Next.js, Vite, TypeScript, Xcode, Rust, Go, and Python. This automatically runs appropriate checks to catch style violations and type regressions.

Sequential gate enforcement works by ordering four gates—compile, lint, type-check, and bundle—where each gate must pass before proceeding to the next. This strict ordering prevents broken code from advancing through the build pipeline.

Build quality gate logs and exit codes are stored under the e2e-evidence/build-gates/ directory. This produces per-gate evidence logs and a gate report for audit purposes and downstream verdict-writing agents.

You need a pre-deploy preflight check to prevent deploying broken or poorly packaged code. By enforcing a strict four-stage build pipeline before merge or deployment, you ensure structural quality is validated before functional testing begins.