verify

To verify code changes before declaring completion, run fresh checks for tests, linting, and builds. This workflow collects output evidence matching predefined criteria, ensuring software development claims like feature completion or bug fixes are validated before reporting success.

Automating build verification and lint checks involves running explicit commands that interpret outputs and exit codes. This approach maps results to verifiable evidence, ensuring lints are clean and builds succeed before confirming a software refactor or feature is ready.

You need to run fresh verification checks whenever confirming completion claims for features, bug fixes, or refactors. This structured approach prevents premature success reports by enforcing explicit commands to validate tests, linting, and builds before any results are confirmed.

This verification workflow does not require specific test or build tools, as it operates dependency-free. It enforces explicit commands to run fresh verifications, interpreting the outputs and exit codes of your existing tests, linters, and builds to collect matching evidence.

Collecting evidence before confirming a bug fix prevents error-prone, unverified completion claims. By running fresh checks and mapping outputs to predefined criteria like passing tests and clean lints, you ensure the software changes are truly validated before reporting success.

The limitation of automating completion verification is that it requires predefined criteria and explicit commands to function correctly. Without clear evidence matching rules for tests, linting, or builds, the workflow cannot accurately interpret outputs to confirm software readiness.