check

To check code quality before committing, run a spec-driven check on your changed files to identify applicable modules, enforce lint and typecheck rules, and surface violations against project guidelines stored in the .trellis/spec index.

Spec-driven code review for git diffs is the process of comparing recent changes against a .trellis/spec index to automatically identify deviations from project-specific development guidelines and report violations for remediation.

Yes, you need Python3 and access to the repository's .trellis/spec and script environment to perform diffs, resolve applicable modules, and execute lint and typecheck automation on changed files.

Automated quality assurance finds applicable spec modules by analyzing your changed files, performing module resolution against the .trellis/spec index, and reading the specific quality guidelines to enforce lint and typecheck before commits.

The best way to enforce development guidelines on recent git changes is applying a diff check that compares changed files against the .trellis/spec index to catch drift early and report violations before you commit.