finish-work

A pre-commit quality gate is a validation checkpoint that enforces linting, type checks, tests, and code-spec alignment before code is committed. It acts as a uniform checklist and guardrail to ensure code readiness and traceable validation steps during local development.

To run pre-commit checks locally, execute the finish-work checklist before submitting a commit. This process verifies linting, type-checking, tests, and documentation updates to guarantee code quality and proper spec synchronization prior to pushing changes.

Yes, the pre-commit checklist explicitly verifies code-spec synchronization and enforces cross-layer validation across the development workflow. It ensures infrastructure guardrails are met and documentation is updated before a commit is finalized.

The best way to ensure documentation is updated before a Git commit is to apply a comprehensive pre-commit checklist. This enforces code-spec alignment and traceable validation steps, guaranteeing proper documentation is completed prior to pushing changes.

Yes, you can use this pre-commit guardrail without external dependencies. It operates as a standalone checklist requiring no prior setup, directly enforcing lint, type-check, and test validations within your local Git workflow.

You need to run a comprehensive code readiness checklist when a feature is complete and ready for commit. It enforces guardrails for executable checks, documentation, and cross-layer verification before pushing changes to the repository.