validate-build

Post-build package validation checks structure, package.json fields, and dependency conventions against the spec. It runs tests, executes TypeScript typechecks, and validates dist output to ensure built packages match project specifications and releases remain consistent.

Monorepo build verification checks package.json fields, enforces dependency conventions, and detects banned dependencies or source anti-patterns. It ensures the package adheres to project specifications before publishing.

Yes, you can automate post-build validation by running a checklist that produces a report of passed checks, failing files with line references, and recommended fixes. This runs after CI build to verify structure, tests, and artifacts before publishing.

Yes, validate-build enforces kernel and phase signatures specifically for reasoning-related packages. It validates these specific rules alongside standard test execution and TypeScript typechecks.

The best way to enforce coding patterns is to validate source files against the spec, checking for anti-patterns and banned dependencies. This ensures the package matches runtime expectations and required project conventions.

Build verification fails when the package structure lacks required source files, contains anti-patterns, or produces invalid dist output. The validation checklist returns failing file paths with line references and remediation steps to fix these mismatches.