finish-work

Pre-commit checks for lint, type-check, and tests are executed by running the finish-work workflow, which validates all quality gates before code submission. It ensures changes across code, infra, and database layers pass end-to-end readiness verification.

A pre-commit quality checklist verifies lint, type-check, test suites, and documentation alignment before submission. It applies executable checks, cross-layer specifications, and manual verification steps to guarantee code readiness and prevent regressions.

Yes, the finish-work workflow supports database and infrastructure layers by applying cross-layer specifications and executable checks. It ensures changes across code, infra, and database layers meet end-to-end readiness prior to commit submission.

Code-spec synchronization is enforced by the pre-commit workflow through manual verification steps and cross-layer checks. This prevents regressions by aligning repository standards, documentation, and executable test suites before code submission.

Yes, the pre-commit workflow operates without additional dependencies, requiring no external components or modules. It directly enforces lint, type-check, test, and documentation alignment gates on your existing codebase.

Manual verification steps are needed in a CI workflow to complement executable checks and enforce code-spec synchronization. They prevent regressions by validating cross-layer specifications and documentation alignment that automated tests alone might miss.