quality-gate

Quality gates automate validation at critical development checkpoints like pre-commit, pre-merge, and pre-release stages. They enforce linting, formatting, type checking, secrets scanning, and test requirements so that code quality, documentation, and security criteria must pass before any merge or release proceeds.

Yes, you can run pre-commit checks to enforce linting, formatting, type checking, and secrets scanning before code is committed. Issuing /quality-gate pre-commit triggers these validations automatically, preventing developers from committing code that violates configured quality or security rules.

Pre-release verification automates comprehensive validation prior to releasing software by checking quality, documentation, and security gates. Running /quality-gate pre-release with a semantic version ensures all configured criteria pass before that specific version is released, preventing unverified code from reaching production.

Yes, this skill supports configurable checks and integration with existing CI/CD pipelines. It applies automated validation at pre-commit, pre-merge, pre-release, and post-release gates without requiring external dependencies, fitting into your current development workflow alongside existing pipeline stages.

Pre-merge validations require successful tests, code reviews, and documentation updates before merging. Running /quality-gate pre-merge with a pull request number checks that all configured governance criteria are satisfied for that PR, blocking the merge until QA requirements pass.