verification-before-completion

To prevent premature code completion claims, enforce a strict verification process requiring fresh evidence from test suites and build commands before asserting any task success. This protocol mandates executing verification commands and critically examining their output to confirm factual accuracy and reduce errors.

Running verification commands before claiming a bug fix is complete ensures factual accuracy by providing fresh, verifiable evidence. This process enforces an evidence before claims protocol, preventing rationalizations and shortcuts that lead to false positives, thereby reducing errors and building trust in the work.

The best way to verify code quality before creating a pull request is to run relevant test suites, linters, or build commands and critically examine the output. This mandatory verification process ensures that all completion claims are backed by fresh evidence, preventing premature success declarations.

A gate function enforces evidence before assertions by acting as a mandatory checkpoint that prevents premature status claims. It requires the execution and review of verification command outputs, ensuring all success declarations in testing and bug fixing are backed by fresh, verifiable evidence.

To identify red flags and shortcuts leading to false positives in code review, enforce a strict evidence before claims protocol. This process helps users recognize and avoid common rationalizations by mandating the execution and critical examination of verification commands prior to any assertion of completion status.

You need to enforce a strict verification process for task completion during all stages of software engineering work, including testing, bug fixing, and build processes. This protocol mandates running verification commands before asserting success to prevent premature declarations and ensure factual accuracy.