oc-bug-check

To automate pre-commit QA for staged Git changes, you can run a suite of code quality checks including type safety, linting, and tests. This prevents low-quality commits from reaching production by blocking failures.

A pre-commit hook for TypeScript projects should run type checking, ESLint linting, Prettier formatting, Vitest tests, secret detection, and build verification. These checks ensure error-free commits by validating staged changes.

Yes, you need ESLint, Prettier, TypeScript, Vitest, and npm installed. These dependencies provide the core type checking, formatting, linting, and testing capabilities required to validate staged changes.

Yes, you can block Git commits that fail linting and testing checks. Blocker management prevents commits with failures, only allowing passes or warnings, ensuring code quality standards are met.

The best way to run fast QA checks on staged files is to use an automated pre-commit hook that completes validation in under 2 minutes. This provides immediate feedback on code quality without delaying commits.

Pre-commit hooks may miss type errors and anti-patterns if they do not execute TypeScript type checking and anti-pattern detection on staged changes. Automating these checks ensures failures are caught before committing.