finish-work

To enforce a pre-commit checklist, you need a structured workflow that runs lint, typecheck, and tests while verifying prerequisites and surfacing follow-up items before code submission. This ensures code quality checks catch issues early.

The best way to ensure documentation sync before a commit is to run a pre-commit validation flow that verifies docs and changelog references stay aligned with code changes, preventing outdated documentation from reaching your repository.

No, a pre-commit validation flow can run without external dependencies, operating independently without writing artifacts or using memory while verifying completion and surfacing follow-up items after checking code quality.

You verify code quality and prerequisites prior to code submission by executing pre-checks that read referenced docs and scripts, followed by running lint, typecheck, and tests to catch issues before committing.

You need a pre-commit workflow for code quality checks during standard software development whenever you want to catch issues early, verify completeness, and ensure documentation and changelog references are aligned before submitting code.

Running pre-commit checks without writing artifacts means the validation process operates statelessly, focusing solely on verifying completion and surfacing follow-up items rather than generating persistent reports or modifying project files during the check.