verification-before-completion

Verifying software testing completion claims with fresh evidence requires running a full verification command and inspecting its outputs. This skill enforces evidence-based completion by validating exit codes and capturing command outputs before asserting success.

Evidence-based verification in development pipelines is the practice of proving status claims with actual command outputs. It prevents false positives by requiring fresh verification runs and inspecting outputs before declaring a build successful or a bug fixed.

Preventing false positives in deployment pipelines requires a gate-like workflow with mandatory checks. You must run verification commands, validate exit codes, and document the evidence before declaring completion to ensure claims are not premature.

Yes, the verification process applies across development, testing, and deployment pipelines. It enforces running a full verification command, inspecting outputs and exit codes, and documenting evidence before declaring success in any pipeline stage.

Automated builds report success without command output evidence when completion claims are premature without explicit verification. This skill enforces evidence-based completion by requiring fresh verification outputs before allowing a success assertion.