verify

To run code quality checks before committing changes, execute the /verify command. It confirms code quality by running linting, testing, and type checking to ensure your changes meet intended goals and pass all necessary conventions.

The best way to automate linting and testing before a git commit is using a quality gate process. This approach validates code changes against defined conventions and provides immediate feedback on whether the change should be committed.

Yes, you need specific linting, testing, and type checking tools installed in your environment to verify code quality. The verification process requires these external tools to execute checks and validate that your code meets defined conventions.

Yes, you can use this verification process in continuous integration workflows and code review processes. It executes necessary checks like linting and type checking to confirm code changes achieve their desired outcomes before integration.

Code may fail verification checks even when tests pass because the process also runs linting, type checking, and rules sanity checks. Failing any of these defined convention checks or task confirmation validations will prevent a successful verification.