verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: zjuxjy

Verify command outputs before claiming task completion or success.

Updated Feb 27, 2026

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

Ready to run

npx skills add https://github.com/ZJUxjy/opencode_lite --skill verification-before-completion-zjuxjy

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Enforces Verification: Mandates running specific commands and checking their output before declaring a task, bug fix, or build as complete.
Prevents False Claims: Guards against common rationalizations and "red flag" behaviors that lead to shipping incomplete or broken work.
Use Case: Before committing code, the agent must run the test suite and confirm zero failures, then verify the build command exits with code 0, before stating "Build and tests passed."

Quick Start

Always run the verification command and check its output before claiming any status or expressing satisfaction.

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 AI agents from falsely claiming code review and testing completion?▼

Enforce verification before completion by mandating explicit command execution and output checks. This prevents premature success assertions by requiring test suites to pass and build commands to exit successfully before reporting status.

What is the best way to ensure build verification and quality assurance before committing code?▼

The best way to ensure build verification is applying an evidence before claims policy. Run specific commands, confirm zero test failures, and verify the build exits with code zero before declaring any task complete.

How do I stop false status reporting during bug fixing and development?▼

Stop false status reporting by enforcing strict verification checks during bug fixing. Require the agent to execute commands and validate outputs, preventing rationalizations that lead to shipping incomplete or broken work.

Can I enforce linting and test execution checks before a development task is marked complete?▼

Yes, you can enforce linting and test execution before completion. The verification policy applies to all development stages, requiring commands to run and outputs to be checked before any task success is claimed.

Why does my agent claim work completion without running the build or test suite?▼

Agents claim completion without running builds due to common rationalizations and red flag behaviors. Enforcing an evidence before claims policy mandates explicit command execution to prevent these premature assertions of success.