finish-work

A pre-commit quality checklist coordinates lint, type-check, and test validation to prevent incomplete commits. You run deterministic checks across API changes and migrations to guard against infra drift and ensure code meets quality gates before release.

Code-spec synchronization verifies documentation and specifications are updated in tandem with code changes. Cross-layer verification ensures migrations and infra layers remain in sync, preventing drift between the implementation and the documented spec before commit.

Inconsistent pre-commit quality checks cause broken builds, flaky tests, and spec drift. Enforcing a comprehensive checklist validates API changes and cross-layer dependencies, requiring documentation of check results and failures to prevent incomplete commits from entering the main branch.

Yes, the pre-commit workflow requires documentation of deterministic check results and failures. It enforces validation of API changes and migrations, ensuring all cross-layer verifications and code-spec synchronizations are explicitly recorded before the code is committed.

Yes, you can guard against infra drift during release preparation by running deterministic checks. The workflow enforces cross-layer verification across migrations and infrastructure layers, ensuring all components are in sync before finalizing the commit.

Cross-layer verification for migrations and API changes is needed during code review and release preparation. Running deterministic pre-commit checks ensures infrastructure layers remain synchronized and prevents incomplete commits from causing broken builds or flaky tests.