verification-before-completion

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

Enforce verification evidence before claiming completion in software workflows.

Updated Nov 14, 2025

Search Tags:#code quality #testing #quality assurance #ci/cd #developer workflow #verification

Ready to run

npx skills add https://github.com/ernitpt/ernit_test --skill verification-before-completion-ernitpt

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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

Core Features & Use Cases

Mandatory Verification: Enforces a strict "evidence before claims" principle.
Gate Function: Outlines a clear, step-by-step process for verification before any assertion of completion.
Use Case: Before committing code, you must run npx tsc --noEmit && npx eslint src/ --ext .ts,.tsx and confirm the output shows no errors, preventing the submission of broken or non-compliant code.

Quick Start

Always run the verification commands and check the 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 broken TypeScript code from being submitted in a developer workflow?▼

To prevent broken TypeScript code from being submitted, enforce a strict verification process requiring fresh evidence before completion claims. You must run commands like `npx tsc --noEmit` and `npx eslint src/ --ext .ts,.tsx` to validate code quality.

What is the Iron Law of verification before completion in software engineering?▼

The Iron Law of verification before completion is the principle that no completion claims can be made without fresh verification evidence. This quality assurance mechanism mandates executing specific validation commands to prove work success.

How to verify code quality before claiming an agent task is complete?▼

To verify code quality before claiming an agent task is complete, follow a strict gate function process. Execute mandatory verification commands like `npx tsc --noEmit && npx eslint src/ --ext .ts,.tsx` and confirm the output shows zero errors.

Does the verification process work with CI/CD pipelines for quality assurance?▼

Yes, the verification process integrates with CI/CD pipelines for quality assurance by enforcing an evidence-before-claims principle. It applies to software development workflows, requiring fresh validation outputs before any success assertions are made.

When do I need to run fresh verification evidence during development?▼

You need to run fresh verification evidence during development whenever you are ready to claim work completion or success. This prevents premature declarations of finished tasks and ensures all defined criteria are validated.

Why does claiming completion without verification cause costly errors?▼

Claiming completion without verification causes costly errors because it allows broken or non-compliant code to bypass quality assurance checks. Enforcing mandatory verification steps maintains honesty by requiring actual command outputs before any success assertions.