verification-before-completion

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

Run fresh verification commands and review output before claiming task completion.

Updated Apr 18, 2026

Search Tags:#code quality #testing #development workflow #verification #pull requests #bug validation #completion claims

Ready to run

npx skills add https://github.com/sammy9322/ventura-dental-facturacion --skill verification-before-completion-sammy9322

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/sammy9322/ventura-dental-facturacion/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/sammy9322/ventura-dental-facturacion --skill verification-before-completion-sammy9322

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of developers or AI agents claiming work is complete, fixed, or passing without running actual verification, which leads to shipping broken code, missing critical requirements, and breaking trust with team members and collaborators.

Core Features & Use Cases

Iron Rule Enforcement: Mandates that no completion, success, or satisfaction claims can be made without fresh, full verification command output as evidence.
Step-by-Step Gate Function: Provides a clear 5-step process to identify the correct verification command, run it fully, review output, confirm results, and only then make claims.
Failure Prevention Guides: Includes common failure scenarios, red flags to watch for, and rationalization prevention tips to avoid skipping verification steps.
Use Case: Before committing code changes or creating a pull request, use this Skill to run your test suite, confirm 0 failures, and only then claim the tests pass, avoiding broken code from being merged.

Quick Start

Use the verification-before-completion skill to confirm your latest code changes pass all required tests and linting checks before submitting a pull request for review.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I verify code changes before creating a pull request?▼

Verify code changes before a pull request by running your test suite, reviewing the full command output for failures, and only claiming completion if zero failures are present with explicit evidence.

Why does claiming a bug fix is complete without verification break team trust?▼

Claiming a bug fix is complete without verification breaks team trust because it risks shipping defective software and missing requirements. Backing success claims with fresh verification output ensures reliability and transparency.

What is the best way to validate bug fixes before committing code?▼

The best way to validate bug fixes before committing code is to execute fresh verification commands, review the full output for failures, and confirm results. This ensures no unverified completion claims result in defective software shipments.

How do I stop AI agents from claiming work is complete without running tests?▼

Stop AI agents from claiming work is complete without running tests by enforcing a step-by-step gate function that requires fresh verification command execution, full output review, and success claims backed by explicit evidence.

Can I use this verification process for agent work delegation in development workflows?▼

Yes, you can use this verification process for agent work delegation. It applies to all software development tasks including code commits, pull request creation, and bug fix validation by requiring fresh verification commands and explicit evidence.

What are common failure scenarios when skipping verification before completion claims?▼

Common failure scenarios when skipping verification before completion claims include shipping broken code, missing critical requirements, and breaking team trust. Red flags and rationalization prevention tips help avoid skipping verification steps.