verification-before-completion

To enforce running tests before claiming code completion, this Skill mandates executing verification commands like linters or build tools to produce fresh evidence, preventing premature assertions of success or correctness in your development workflow.

Evidence-based verification in CI/CD pipelines is a process requiring concrete output from verification tools before any success statement is made. It ensures claims of passing tests, clean linters, or successful builds are always backed by fresh command execution results.

You prevent premature assertions of fixed bugs and successful builds by enforcing a rigorous verification process that mandates the execution and review of specific commands to produce fresh evidence before any claims of task completion or correctness are made.

Yes, this verification process works with standard linters and build tools. It mandates executing specific commands like shellcheck to confirm zero errors in the output, ensuring your code meets defined criteria before you state that work is complete.

Relying on manual code quality checks risks unverified code, incomplete features, and broken builds. This Skill addresses these limitations by requiring concrete output from verification tools, ensuring work meets defined criteria before any success statement is made.