verify

Verify code changes by running checks in a defined order: existing tests, typecheck/build, targeted command verification, and manual observable validation. This evidence-first workflow ensures you report only proven results, including failures or explicitly unverified items, preventing mistaken completion claims.

Validating a refactor requires transparent reporting of what was actually verified. Run existing tests first, then build and typecheck checks, followed by targeted commands, documenting what passed, what failed, and what remains unverified to build true refactor confidence.

Turn vague completion claims into concrete observations by applying an evidence-first verification workflow. Specify the behavior that must be proven, run recommended checks sequentially, and report only the pass/fail outcomes you actually observe rather than relying on assumptions.

Manual validation is used when automation cannot fully cover the behavior. The verification process starts with automated tests and typecheck/build, then proceeds to targeted command checks, and finally applies manual observable validation to ensure evidence-first confidence for feature development.

A passing build alone does not guarantee verified behavior. True verification confidence requires running checks in a defined order including existing tests, typecheck/build, and targeted command verification, ensuring all changes produce the intended behavior before marking work complete.