verification-before-completion

Require fresh verification evidence before claiming work completion or passing tests.

26|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/BinyaminEden/claude-combine --skill verification-before-completion-binyamineden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/BinyaminEden/claude-combine/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/BinyaminEden/claude-combine --skill verification-before-completion-binyamineden

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the pervasive issue of developers and AI agents making unsubstantiated claims that work is complete, tests pass, bugs are fixed, or builds succeed without running actual verification. This behavior leads to broken code being shipped, wasted time on rework, and broken trust between collaborators and AI assistants.

Core Features & Use Cases

  • Mandatory Verification Gate: Enforces a strict 5-step process that requires running fresh, full verification commands, checking exit codes and full output, and providing evidence before any completion or success claims are made.
  • Anti-Rationalization Guardrails: Lists common excuses for skipping verification (e.g., "I'm confident", "Just this once") and their rebuttals, plus clear red flags to stop invalid claims before they happen.
  • Use Case: Apply this Skill before committing code, creating pull requests, delegating tasks to AI agents, or claiming a bug is fixed to ensure only verified, working work is marked as complete.

Quick Start

Use the verification-before-completion skill to confirm all tests pass and the build exits successfully before you claim your recent code changes are ready to commit.

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 claiming code is complete without running tests?

Enforce a mandatory verification gate requiring AI agents to execute full test commands, check exit codes, and provide output evidence before asserting any task is complete. This prevents unverified code from being committed or shipped.

What is build verification and when do I need it before a code commit?

Build verification executes full build and test commands to confirm code integrity. You need it before any code commit, pull request creation, or bug fix claim to ensure changes actually work and prevent broken code from being shipped.

How to verify test validation passes before creating a pull request?

Run fresh, full test suite commands, explicitly check exit codes, and review complete output. Only after capturing this evidence should you proceed with creating a pull request or claiming that test validation passes.

Why do developers skip pre-commit checks and how to stop rationalization?

Developers skip pre-commit checks by rationalizing with excuses like high confidence or urgency. Stop this by applying anti-rationalization guardrails that list common excuses alongside rebuttals and red flags to block invalid success claims.

Does this verification process work with any software development workflow?

Yes, this verification process applies to all software development workflows. It enforces a mandatory gate function for code commits, pull request creation, AI agent task delegation, and build validation across various development environments.