verification-before-completion

Enforce a verification protocol before claiming work completion.

Updated May 31, 2026
One-click install
npx skills add https://github.com/thbeh/coding-agents-databricks-apps --skill verification-before-completion-thbeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/thbeh/coding-agents-databricks-apps/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/thbeh/coding-agents-databricks-apps --skill verification-before-completion-thbeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill promotes honesty and transparency by enforcing a verification process before claiming work is complete, fixed, or passing.

Core Features & Use Cases

  • Verification Protocol: Provides a structured verification process with clear steps for ensuring claims are backed by evidence.
  • Pre-Commit Checks: Encourages running verification commands and confirming output before making any success claims.
  • Guidance for Failure Prevention: Offers guidance on common pitfalls and rationalizations to prevent false claims.

Quick Start

Run the verification command and ensure all checks pass before claiming 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 ensure code integrity before creating a pull request?

To ensure code integrity before creating a pull request, follow a strict verification protocol requiring evidence-based output from tests and checks before claiming completion. This prevents false success claims.

What is an evidence-based verification process in software development?

An evidence-based verification process in software development is a structured protocol enforcing command execution and output confirmation before claiming work is fixed or passing.

How do I prevent false claims when completing bug fixes?

To prevent false claims when completing bug fixes, adhere to a defined verification protocol that guides past common pitfalls and rationalizations by requiring concrete command output as proof of success.

What pre-commit checks should I run for feature implementations?

Pre-commit checks for feature implementations should involve running structured verification commands and confirming all checks pass with concrete output before making any success claims.

Are there limitations to using a strict verification protocol before commits?

A strict verification protocol before commits requires adherence to running commands and validating output; its limitation is potential bypass if developers rationalize skipping steps when facing common pitfalls.