verify

To verify task outputs for correctness, systematically recheck original requirements, execute tests, and review edge cases. This process confirms completeness by validating formatting, linting, and type safety to ensure the work is ready to deliver without regressions.

Quality assurance verification is a final review pass that checks generated code against expected outcomes. It applies after feature implementation or refactoring to catch missing requirements, error handling gaps, and type safety issues before shipping.

You need to run a regression and test coverage check after completing feature work, refactoring, or cleanup tasks. This final correctness pass rechecks requirements and edge cases to reduce the risk of introducing new defects into the codebase.

Yes, you can use automated verification for refactoring and code cleanup tasks. It systematically rechecks the original task requirements, validates tests, and inspects edge cases to ensure the refactoring did not break existing functionality or formatting.

The best way to catch missing requirements and linting issues is to apply a systematic completion review. This verification step rechecks the original task, validates test coverage gaps, and enforces type safety and formatting standards before delivery.