gate

To run pre-merge quality gate checks, execute the gate skill with your story ID as an argument. This triggers automated code reviews and security checks to ensure changes meet quality standards before merging into the main branch.

An automated code review process includes syntax checking, style checking, and unit testing. These checks are executed during the pre-merge quality gate to verify that code changes adhere to established standards before integration.

Yes, you can use automated security checks to identify potential vulnerabilities before merging. The quality gate performs these security evaluations alongside code reviews to ensure changes are safe for the main branch.

A CI/CD pipeline is not strictly required to execute quality gate checks. While intended for CI/CD pipelines, you can also manually run the gate skill before merging code changes into the main branch.

Before running a pre-merge review process, you need to set up proper reviewer agents and establish the review context. This configuration is required for the quality gate to execute its automated checks successfully.