trellis-check

Pre-commit quality checks identify changed code and trigger verification by applying lint, type-check, tests, and cross-layer safety checks across affected packages. This enforces spec compliance and consistency before committing changes.

Cross-layer data flow validation checks consistency across affected architectural layers during quality verification. It enforces pre-commit style and ensures data moving between layers complies with project specifications and safety standards.

Enforcing spec compliance and linting requires stepwise guidance to assess changed packages, read specs, and run lint and type checks. This guarantees alignment with project standards before code integration.

Yes, quality verification targets affected packages specifically. It identifies changed code and applies type checks and tests only across those impacted layers, ensuring comprehensive safety validation without checking the entire repository.

Validating code consistency across architectural layers requires cross-layer safety checks during the pre-commit phase. This process verifies data flow and enforces style consistency across affected packages to guarantee alignment.

Comprehensive quality checks in CI-CD pipelines ensure spec compliance, linting, type checks, and tests pass across affected packages. This structured process verifies cross-layer consistency and prevents integration of non-compliant code.