finish-work

To automate pre-commit checks, you can run a comprehensive checklist that validates linting, type checking, and tests before committing. This ensures code quality by executing pnpm-based commands and verifying cross-layer specifications to prevent broken builds.

Spec synchronization verifies that executable specifications in .trellis/spec directories include signatures, validation matrices, and test cases. It is needed before a git commit to ensure infra or cross-layer specifications remain executable and accurately reflect code changes.

Yes, pre-commit checklist validation requires a pnpm-based environment to execute lint, type-check, and test commands. It also depends on .trellis/spec directories to perform executable specification verification for cross-layer spec validation.

You can verify API updates and database migrations by running a pre-commit checklist that validates code quality and cross-layer specs. This process checks that all API changes and database migrations are complete and synchronized before the final git commit.

No, this pre-commit validation workflow explicitly requires pnpm to run its lint, type-check, and test commands. Without a pnpm-based environment, the comprehensive checklist cannot properly execute the required quality checks.

The best way to ensure documentation and code quality are updated is to apply a pre-commit checklist that validates linting, testing, and spec synchronization. This verifies all console statements, documentation, and cross-layer specs are complete before committing.