verification-before-completion

Run verification commands and confirm output before claiming task completion.

Updated Oct 21, 2022

Search Tags:#testing #quality assurance #code review #verification #completion #assertions

Ready to run

npx skills add https://github.com/Chengxufeng1994/dotfiles --skill verification-before-completion-chengxufeng1994

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Chengxufeng1994/dotfiles/tree/main/gemini/antigravity/global_skills/verification-before-completion
Command: npx skills add https://github.com/Chengxufeng1994/dotfiles --skill verification-before-completion-chengxufeng1994

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of work completion, ensuring that all verification steps are performed before any assertion of success, thereby maintaining honesty and preventing costly errors.

Core Features & Use Cases

Mandatory Verification: Enforces running specific commands to confirm status before making any claims.
Evidence-Based Assertions: Requires concrete output from verification commands as proof before declaring success.
Use Case: Before committing code, running tests, or reporting a bug fix as complete, this Skill ensures you execute the relevant test suite or linter and confirm the output, preventing the accidental shipment of broken or incomplete work.

Quick Start

Always run the verification command and check its output before claiming any work 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 claims of code completion before committing?▼

To prevent premature claims of code completion, enforce a strict verification protocol requiring execution of specific commands and confirmation of their output before reporting success. This ensures evidence-based assertions are made upon task completion.

What is evidence-based verification in software engineering?▼

Evidence-based verification is a development principle requiring concrete output from test suites or linters as proof before declaring success. It enforces running mandatory verification commands to confirm status and prevent the accidental shipment of incomplete work.

How do I verify a bug fix is complete before reporting status?▼

To verify a bug fix is complete, run the relevant test suite or linter and confirm the output. This protocol demands evidence before assertions, ensuring you execute specific commands and validate their results before claiming the work is finished.

Does the verification before completion protocol apply to all stages of development?▼

Yes, the verification before completion protocol applies to all stages of development and task management where work status is reported or committed. It requires adherence to the principle of evidence before assertions across the entire lifecycle.

What are the limitations of relying on assertions without verification commands?▼

Relying on assertions without verification commands leads to premature claims of work completion, compromising honesty and risking costly errors. Without executing tests to confirm output, you might accidentally ship broken or incomplete work.