pre-commit-gate

You can block bad commits by running a pre-commit gate that enforces lint, typecheck, and test execution locally before each git commit. It requires npm lint, typecheck, test commands and a dangerous-pattern-scan.sh script to pass.

You can detect dangerous shell patterns before committing by running the dangerous-pattern-scan.sh script within your pre-commit gate. This safety scan blocks risky shell code from entering your repository locally before the git commit completes.

The pre-commit quality gate works with JavaScript and TypeScript projects using npm scripts and git. It enforces your npm lint, typecheck, and test commands locally, requiring zero errors before allowing a git commit to proceed.

The best way to prevent broken builds and wasted CI cycles is applying a pre-commit gate that enforces lint, typecheck, and test execution locally. This guarantees code quality and blocks bad commits before they are pushed to the repository.

You integrate a commit gate chain for a full quality pipeline by applying this pre-commit gate alongside subsequent gates. It integrates with style guide, code review, language audit, and IP audit gates to enforce comprehensive code quality checks.