Verification Before Completion

Acerca de

This skill institutes a rigorous 'Gate Function' that prevents premature success claims by mandating a philosophy of evidence before assertions. It requires the execution of fresh verification commands—such as tests, linters, or build scripts—and the thorough analysis of their output before any task can be marked as complete. By eliminating assumptions and 'should-be-fixed' statements, it ensures that every commitment, pull request, or status update is backed by verifiable data, maintaining high trust and preventing the shipment of broken or incomplete features.

Características Principales

• Standardizes verification criteria for builds, linters, bug fixes, and agent-delegated tasks
• Requires fresh, complete command execution to replace reliance on previous runs or partial checks
• Identifies linguistic red flags like 'should' or 'probably' that signal unverified assertions
• Implements a mandatory 'Gate Function' workflow to identify and run proof-of-work commands
• 10,553 GitHub stars
• Enforces red-green cycle validation to ensure regression tests fail correctly before passing

Casos de Uso

• Confirming a project-wide build and lint pass before opening a Pull Request
• Verifying that a delegated agent's work meets requirements through independent evidence rather than trust
• Validating a bug fix with fresh test results and evidence before committing code