verification-before-completion

To prevent false completion claims before a pull request, enforce a gate checklist that requires running the authoritative verification command fresh, inspecting full stdout/stderr and exit codes, and attaching explicit evidence prior to asserting success.

Evidence-based verification in developer and CI workflows is the practice of capturing concrete command outputs, exit codes, and diffs to prove a build, lint, or test step passed, preventing inaccurate status reports and regressions.

To enforce a pre-commit verification gate for automation agents, require the agent to execute the exact test or build command, read the full output, and report the result with captured evidence before declaring the work complete.

Yes, this verification checklist applies to code reviewers, individual developers, and automation agents alike, ensuring everyone inspects exit codes and command outputs before committing code or handing off tasks in CI workflows.

The best way to verify bug fixes before handoff is to run the relevant verification command fully, check the full output and exit code for failures, and attach the concrete verification evidence when reporting the task status.