verification-before-completion

To enforce running tests and linting before claiming code completion, this Skill mandates executing verification commands and confirming their output. It requires concrete evidence from builds or test suites before allowing any assertions of work success or correctness.

Developers might claim work is done without verifying test output due to skipping the verification protocol. This Skill solves that problem by enforcing a strict policy of checking command outputs, ensuring honesty and accuracy in all work status updates before completion claims are made.

The best way to verify code quality before a CI/CD pipeline commit is to run independent verification commands and capture their output. This Skill enforces an evidence-based protocol requiring zero test failures or linting errors to be confirmed before any success claims.

Yes, you can use this verification protocol for agile bug fixing and agent task completion. It applies to all stages of development, requiring engineers and agents to run specific commands and present their output as evidence before asserting that a task is fixed or complete.

Evidence-based verification works by requiring concrete output from verification commands to substantiate any assertion of completion. This Skill enforces a strict protocol where engineers must run tests or builds and confirm the results before making claims about correctness or status.