verification-before-completion

To verify code changes before claiming completion, enforce a rigorous verification process requiring specific commands to run and outputs to be reviewed. This prevents premature assertions by mandating evidence before any declarations of success or bug fixes.

Preventing premature bug fix assertions requires a tiered verification process offering Light, Standard, and Thorough levels based on change scope. This ensures tests pass, builds remain clean, and changes align with original requirements before declaring success.

Choosing the right verification level depends on change scope and risk sensitivity. Light verification suits minor tweaks, Standard fits typical updates, and Thorough verification targets high-risk changes requiring extensive testing and code review before completion.

Tiered testing prevents incomplete fixes by mandating running specific commands and reviewing their output before declarations. Applying Light, Standard, or Thorough verification based on change scope ensures code quality and stability by requiring evidence over assumptions.

A thorough verification process for debugging is needed when change scope and risk sensitivity are high. It enforces running comprehensive testing commands and reviewing outputs extensively to prevent regressions or incomplete bug fixes before claiming success.