reality-verification

To prevent completion hallucinations, enforce evidence-backed verification before accepting any completion claim. This requires reproduction, mock-quality checks, and phase-boundary verification to validate that code changes are genuinely complete.

Verification-before-completion discipline ensures outputs are checked with reproduction and evidence-gated verification rather than relying on unchecked assertions. It gates completion claims by requiring concrete proof before accepting task results.

Completion gating for code-change workflows is enforced by requiring evidence-backed verification at phase boundaries. You must execute reproduction and mock-quality checks before any completion claim is accepted as valid.

The reality-verification skill operates as a deprecated backwards-compatible alias. It routes legacy references to the canonical verification-before-completion skill, meaning existing configurations still function but should be updated.

To migrate from the reality-verification alias, update your prompt or configuration to call verification-before-completion instead. This ensures you use the canonical superset logic for evidence-backed verification going forward.

Evidence-backed verification is needed whenever a code-change workflow reaches a completion claim. It prevents false-positive results by requiring reproduction and phase-boundary checks before accepting that a task is done.