quality

Automating linting and unit tests before a pull request requires executing project quality gates using predefined commands. This skill runs these deterministic validation checks to ensure code standards and functionality are met before integration.

Project quality gates are automated validation checkpoints that execute linting, formatting, and testing commands. They validate code standards by running deterministic tasks to ensure functionality and formatting meet project requirements before deployment.

You can run a fast default check instead of the full test suite by scoping the quality gates to lint and unit tests only. This skips optional smoke tests for quicker code validation during development.

You need predefined commands mapped in the project configuration to run code validation checks. The quality gate execution relies on these defined commands for linting, unit tests, and smoke tests to ensure deterministic validation.

The best way to enforce code formatting checks in a CI/CD pipeline is to execute automated quality gates. This skill runs deterministic formatting checks alongside linting and testing to validate code quality before further integration.

Smoke tests are not running during code validation because they are part of the comprehensive full check scope, not the default fast check. You must select the full scope option to include smoke tests alongside linting and unit tests.