dev-verify

To verify code changes before shipping, map expected behavior into a checklist and prove it using prioritized validation: run existing tests, execute typecheck and build commands, perform narrow direct checks, and document manual validation steps with transparent pass or fail evidence.

The best way to prove a refactoring is safe involves running an evidence-backed verification workflow that prioritizes existing tests first, followed by build validation and targeted command checks, ensuring you produce a clear report of what passed and what failed.

Document release readiness evidence by generating a focused summary that explicitly states what was verified, lists the exact tests and commands executed, and transparently reports any failures or areas that remain unverified without overstating completion.

Feature verification often yields vague claims when it lacks an evidence-first workflow, which requires moving from theoretical confidence to concrete proof by running prioritized tests and build validation checks, then transparently documenting any failures.

When build validation fails during code verification, you must report the failure transparently instead of glossing over it, detailing what specifically failed or remains unverified in your evidence-backed validation summary.

You can check release readiness for feature fixes by prioritizing existing automated tests first, then running typecheck and build validation, and finally documenting any remaining manual validation steps to produce comprehensive evidence of completion.