pre-merge-check

Automated quality gates on a pull request are executed by orchestrating lint, tests, and block audits before merge. This ensures compliance and reliability across all blocks, brands, and styles during your code review.

A PR quality gate validates code changes by coordinating linting, tests, and block audits prior to merge. It applies to all pull requests across blocks, brands, and styles to ensure consistent quality and compliance.

Yes, pre-merge checks enforce lint coverage and test success across multiple brands, styles, and blocks. The quality gate applies to all pull requests and provides a clear pass or fail outcome with actionable feedback.

Automating block audits and token validations during a CI workflow is handled by orchestrating these checks as a final quality gate before merge. It satisfies requirements for audit execution and token validations across all pull requests.

A final quality gate is needed to orchestrate lint, tests, and block audits together, providing a clear pass or fail gate with actionable feedback. This guarantees compliance and reliability before merge across all blocks and brands.

Yes, the pre-merge quality gate works with existing block audit and quality audit skills by orchestrating their checks to validate changes. It coordinates these skills to ensure consistent quality and compliance prior to merge.