quality-gate

Pre-merge quality checks are automated validation steps including linting, type checking, testing, and security audits that ensure code meets required standards before being merged into the staging environment.

Pre-merge quality assurance includes code linting, type checking, testing with coverage validation, build verification, security audits, and UI design and accessibility compliance checks.

To run pre-merge checks for staging integration, execute the quality-gate skill in your repository root directory to validate code and UI components against required standards.

Yes, the pre-merge quality gate checks UI components for adherence to design specifications and accessibility standards alongside code linting, type checking, and security auditing.

Yes, you can use this pre-merge quality gate without external dependencies, as it operates independently using scripts to automate code review and UI testing checks for staging integration.

Pre-merge quality checks fail during build validation and security audits when the build process is unsuccessful or security vulnerabilities are detected in the code before staging integration.