verify-quality

To automate code quality checks before merging, run predefined quality gates that execute linters, type checkers, and test suites against your codebase. This verifies adherence to project requirements and standards before integration or review.

Yes, you can run linting and type checking on a scoped part of your codebase. The quality validation process supports scoped checks, allowing you to target specific areas rather than evaluating the entire project at once.

To use custom quality standards for code review, the validation process reads project-specific commands from way-of-working adoption files and universal standards from quality-standards guidelines to execute your custom quality gates.

A quality gate in automated testing and code review is a predefined validation checkpoint that runs linters, type checkers, and test suites. It ensures the codebase meets project requirements and standards before integration.

Yes, automated quality assurance works without external dependencies. The validation process reads universal standards from quality-standards guidelines and project-specific commands directly from adoption files to execute checks.

A quality gate status report provides detailed feedback on the validation execution. It outlines the pass or fail status of linting, type checking, and testing checks performed against your predefined codebase standards.