verification-before-completion

To enforce test verification before a git commit, this Skill requires running the exact verification command fresh and checking its output before asserting work is complete. It acts as a completion gate for PR readiness by blocking claims unless proven by passing build, lint, or test results.

Preventing false completion claims in a CI workflow requires evidence-before-assertions enforcement. This Skill blocks common failure patterns like rationalizing partial outputs or trusting agent success, ensuring release readiness is strictly matched to confirmed command exit codes and outputs.

Code review processes fail when relying on previous test outputs because this verification mechanism enforces running the full validation command immediately before asserting a fixed status. Anti-rationalization guardrails block using stale data or assuming tests should pass without fresh execution proof.

Yes, you can use this to validate software testing requirements before pushing code. It applies specifically to development workflows where tests, linters, builds, or requirements must be proven immediately before commit, push, or PR creation by checking the exact command output.

Yes, this verification process works without adding external dependencies. It operates directly within your existing development workflow by enforcing that the full verification command is run fresh and its exit code is checked before any passing status is communicated.