check

Cross-layer consistency checks validate data flow, code reuse, and dependency correctness when changes span multiple architectural layers. This optional feature ensures same-layer consistency and prevents structural drift during complex, multi-layer coding sessions.

You use this validation skill after writing code and before committing, especially when session context may have drifted during long or complex coding tasks. It produces a clear report of guideline violations and drives fixes by re-running checks until resolved.

Yes, this validation approach works directly with existing .trellis spec modules by discovering applicable spec files and following each module's defined Quality Check section. It uses git diff to map changed files to the correct specification modules.

You should run spec compliance checks after implementation and before committing, or whenever session context may have drifted. Running checks at these points prevents quality drift and ensures the code satisfies all project-level development guidelines.