trellis-check

To validate code quality before a commit, run a check against recently written code to verify linting, type checks, tests, and cross-layer consistency. This process ensures changes align with project specs and prevents regressions.

Cross-layer data flow validation verifies that data interactions across different architectural layers remain consistent. It detects context drift during ongoing development and provides remediation guidance when issues are found.

Prevent context drift during long-running sessions by validating recently written code against project specs and guidelines. Running quality checks mid-session detects drift early and prevents regressions before committing.

Yes, you can identify changes since the last commit and pull relevant specs to compare against. The check executes lint, type, and test validations, then compares the results against your spec guidelines.

The best way to enforce end-to-end consistency is running a pre-commit validation that checks lint, types, tests, and cross-layer data flow. This detects drift and ensures alignment with project guidelines before changes are committed.