verification-before-completion

To verify code completion before making assertions, you must run the relevant test suite independently and confirm the executed command output shows zero failures before claiming success. This enforces a strict protocol requiring fresh evidence rather than assumptions.

Common red flag behaviors that lead to false completion claims include rationalizing failed tests or assuming successful builds without executing commands. Identifying these flags enforces mandatory verification by requiring fresh command output to validate linting or bug fixes.

You enforce a strict verification process for linting and building tasks by independently executing the commands and validating their output. This provides fresh evidence of clean linters and successful builds before any success statements are made.

You need to verify execution output before committing code or creating a pull request whenever a task involves testing, linting, building, or bug fixing. This prevents premature claims by backing all assertions with actual executed command output.

Yes, this verification protocol applies to all stages of development and bug fixing. It requires independent execution and validation of commands to provide evidence before any success statements are made, preventing costly rework.