What problem does it solve? After writing code, it is easy to miss spec violations, broken tests, leftover debug logging, or inconsistencies across architectural layers. This Skill provides a structured quality verification workflow that catches these issues before committing changes. ## Core Features & Use Cases - Spec Compliance Verification: Reads applicable Trellis spec indexes and guideline files for each changed package or layer to confirm the code follows documented conventions. - Project Checks: Runs the project's lint, type-check, and test commands and requires all failures to be fixed before proceeding. - Cross-Layer Review: Checks data flow (Storage → Service → API → UI), code reuse, import/dependency correctness, and same-layer consistency when changes span multiple layers. - Use Case: After implementing a feature touching the API and UI layers, run this check to confirm types propagate correctly, tests were added for new functions, and the spec docs are updated with any lessons learned. ## Quick Start Run the trellis-check quality verification on my recent uncommitted changes and fix any violations found.
