ship-preflight

You can run automated pre-flight checks to catch TypeScript build regressions and Prisma schema mismatches before requesting human code review. This validates type safety, test hygiene, and cross-layer consistency on feature branches.

Pre-review code hygiene validation is an automated process that detects forbidden patterns like `any` types, `console.log` statements, and `.only()` test calls in full-stack TypeScript projects to enforce project-specific coding standards before review.

Cross-layer consistency guards verify alignment between frontend mutation data shapes and backend Zod validation schemas. This automated check prevents silent persistence failures by ensuring both layers expect matching data structures.

Yes, automated regression testing works with Prisma and Zod schemas by matching migration foreign key constraints to Prisma schema definitions and validating backend Zod schemas against frontend data shapes across separated API and web layers.

Hidden type regressions exist because standard builds often use stale caches and skip test file compilation. Clearing caches and forcing TypeScript compilation across web, API, and test files exposes these regressions before review.

Automating pre-flight checks via a dedicated validation process runs final technical checks on feature branches, catching over ten common issues including type errors and schema mismatches in seconds before a human reviewer is involved.