verification-before-completion

Verify completion claims by running build, test, and lint commands, reading full outputs, and reporting outcomes with concrete evidence before finalizing a pull request. This enforces honest status signaling and prevents premature task declarations.

Evidence-based status verification requires running explicit build, test, and lint checks, then documenting the actual outcomes to justify any completion claim during code reviews. It guards against false positives and enables traceable accountability.

Prevent false completion claims by applying a repeatable verification workflow that executes build, test, and lint checks before task handoffs. Documenting the actual command outputs provides traceable accountability and blocks dishonest or premature success signals.

Yes, verification before completion requires running explicit build, test, and lint verification commands. Reading the full command outputs and reporting the actual outcomes with evidence is mandatory to justify any completion claim.

The best way to ensure honest status signaling is to enforce a verification checklist that runs build, test, and lint checks, then reports actual outcomes with concrete evidence before declaring completion. This provides traceable accountability for code reviews and pull requests.