Finish Work - Pre-Commit Checklist

A pre-commit checklist validates code quality by running pnpm lint, pnpm type-check, and pnpm test to ensure changes pass quality gates before committing. It flags leftover console logs, verifies type safety conventions, and checks cross-layer behavior.

Spec synchronization ensures backend and frontend documentation stays consistent with code changes. You need it before committing when updates touch APIs, database migrations, or shared contracts to prevent incomplete cross-layer modifications.

To verify database migration correctness and API changes before committing, run a pre-commit validation that enforces executable contracts, validation matrices, and required test points for infrastructure updates to ensure cross-layer consistency.

Yes, this pre-commit workflow explicitly requires pnpm to run lint, type-check, and test commands, while enforcing TypeScript type safety conventions and checking for unsafe patterns before allowing a commit.

The best way to ensure test completeness is running a pre-commit check that promotes adding unit, regression, or integration tests whenever logic or behavior changes, verifying that all modified code paths are covered.

You need to remove console logs before a git commit because leftover debugging statements violate code quality conventions and can leak sensitive runtime data, which the pre-commit verification actively flags as an issue to block committing.