verify-changes

Automated verification runs ESLint, TypeScript compilation checks, and unit tests after code modifications to ensure code integrity and prevent bugs. It mandates these checks to maintain a high standard of code before changes are considered complete.

Running automated linters and test suites verifies refactored code changes by enforcing coding standards and confirming no new issues are introduced. This process provides clear status reporting and failure handling guidance.

Automated verification directly executes ESLint and TypeScript compilation checks alongside unit tests. It provides clear guidance on how to address failures from any of these checks to maintain coding standards.

TypeScript compilation checks fail during automated verification when type errors are introduced during code modification. The verification process reports these failures clearly and provides guidance on how to address the specific TypeScript issues.

You need to run linters and type checkers after every code modification in a development workflow requiring adherence to coding standards. This automated verification prevents bugs and maintains a high standard of code correctness before changes are considered complete.