trellis-check

Run a structured check that identifies changed files with git diff, reads applicable specs, then executes the project's lint, type-check, and test commands. Finish with a checklist covering debug logging, suppressed warnings, and test coverage for new or changed behavior.

Trace read flows from Storage through Service and API to UI, and write flows in reverse. Confirm types and schemas pass correctly between layers and that errors propagate to the caller rather than being swallowed.

Skip cross-layer analysis when the change is confined to a single layer. The data flow, code reuse, and import dependency dimensions only apply when changes touch three or more layers or create new shared utilities and files.

New functions require unit tests, bug fixes require regression tests, and changed behavior requires updating existing tests. The verification checklist enforces each of these cases explicitly before the change is considered complete.

Documenting non-obvious fixes and newly discovered patterns in the spec directory prevents repeating the same mistakes. If a future session would benefit from the lesson, the relevant spec file should be updated during the quality check.