verification-before-completion

Run verification commands and validate output before declaring task completion.

Updated Aug 23, 2026

Search Tags:#testing #quality assurance #ci/cd #code review #verification #completion

Ready to run

npx skills add https://github.com/pearjelly/turbooknow --skill verification-before-completion-pearjelly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/pearjelly/turbooknow/tree/main/.agent/skills/verification-before-completion
Command: npx skills add https://github.com/pearjelly/turbooknow --skill verification-before-completion-pearjelly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of completion or success by enforcing a strict verification process, ensuring that all assertions are backed by concrete evidence before any commitment or reporting.

Core Features & Use Cases

Mandatory Verification: Enforces running specific commands to confirm test results, build success, bug fixes, or requirement fulfillment.
Evidence-Based Claims: Requires explicit output or exit codes as proof before any statement of completion or satisfaction.
Use Case: Before merging code, this Skill ensures all tests have been run and passed, the build is clean, and the bug is confirmed fixed with verifiable output, preventing the introduction of regressions or incomplete work.

Quick Start

Run the verification command and confirm its output before claiming the task is complete.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent premature code completion claims in CI/CD pipelines?▼

Prevent premature code completion claims by enforcing a strict verification protocol that mandates running specific commands and validating their output before committing or reporting success.

What is evidence-based verification before claiming a bug fix is complete?▼

Evidence-based verification requires explicit output or exit codes as proof that tests pass and builds succeed before any statement of completion or bug fix satisfaction is made.

How to enforce running tests before creating a pull request?▼

Enforce running tests before creating a pull request by mandating verification commands that confirm all tests pass, the build is clean, and requirements are fulfilled with verifiable output.

Why do incomplete features and regressions get shipped despite code reviews?▼

Incomplete features and regressions get shipped because of premature declarations of work status without running verification commands to validate actual test results and build success.

Can I use automated verification to block PR creation if the build is broken?▼

Yes, automated verification blocks PR creation by mandating a clean build and validated test output, ensuring no broken builds or incomplete work are introduced into the codebase.