quality-commit

Automating linting, type checking, and tests before a git commit is done by running a pre-commit quality gate. This Skill sequences linting, type checking, Semgrep scanning, and test execution, committing changes only when all gates pass.

Yes, you can run security scans and type checking on staged TypeScript files in a monorepo. The Skill applies Semgrep scanning and type checking across multi-workspace JavaScript/TypeScript projects, including frontend, API, and shared code.

Semgrep scanning integrates into a pre-commit hook workflow by executing per file during the staged changes evaluation. It acts as a deterministic security gate that runs alongside linting and type checks before allowing an atomic commit.

The best way to add automated code review to a pre-commit quality gate is using an optional review step. This Skill supports optional CodeRabbit review and guidance as part of its configurable commit workflow before finalizing the commit.

Yes, this pre-commit quality gate supports pushing changes directly after checks pass. It implements a guarded commit workflow with configurable flags that include optional push steps once linting, scanning, and test executions succeed.