trellis-check

To automate code quality checks before committing, you can run a structured verification workflow that applies lint, type-check, tests, and spec compliance to recently written code, prompting fixes for any failures before the commit is made.

The best way to enforce spec compliance and lint rules across a multi-layer codebase is to use an automated workflow that guides checks across layers, collects results, and reports inconsistencies to reduce context drift and catch issues early.

Yes, you can run tests and type-checks specifically on changed packages within your repository, allowing the verification process to detect issues early by targeting only the recently written code rather than the entire project.

Pre-commit code review can catch cross-layer data flow issues automatically when integrated with an end-to-end verification workflow that applies structural checks across multi-layer codebases before allowing changes to be committed.

Running end-to-end checks instead of manual code review before a commit ensures consistent enforcement of project standards, reduces human error, and catches context drift or bugs early by automating lint, type-check, and test verification.

To fix lint and test failures reported during pre-commit verification, follow the structured workflow prompts generated by the quality check process, which collect failure results and guide you through resolving issues before committing changes.