verification-before-completion

Enforces evidence-based verification of tests and builds before completion claims.

Updated Aug 23, 2026

Search Tags:#testing #qa #verification #code-quality #developer-workflow #pre-release #commit-checks

Ready to run

npx skills add https://github.com/Whaleylaw/llm-lawyer --skill verification-before-completion-whaleylaw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Whaleylaw/llm-lawyer/tree/main/.claude/skills.old/verification-before-completion
Command: npx skills add https://github.com/Whaleylaw/llm-lawyer --skill verification-before-completion-whaleylaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents false or premature claims of completion by requiring fresh, observable verification evidence (command outputs, exit codes, and reproducible checks) before asserting that work is done.

Core Features & Use Cases

Gate Function: A five-step verification pattern (identify, run, read, verify, then claim) that enforces evidence-first reporting.
Common Scenarios: Use before committing, opening PRs, declaring bug fixes, merging branches, or accepting agent-reported success.
Risk Reduction: Captures red flags, prevents rationalizations, and ensures reproducible proof (test outputs, build exit codes, VCS diffs).

Quick Start

Run the exact verification command for the task, inspect and copy the full output including exit status, and report that evidence before stating anything has passed.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I enforce test verification before declaring a pull request complete?▼

To enforce test verification before declaring a pull request complete, apply a five-step gate function that identifies, runs, and reads the full verification command output, ensuring all exit codes and reproducible checks pass before claiming success.

What is the best way to prevent false claims about passing builds in a developer workflow?▼

The best way to prevent false claims about passing builds is to require fresh, observable verification evidence such as command outputs and exit codes before asserting that work is done, eliminating premature or unverified success statements.

How do I verify code quality checks before committing changes to version control?▼

To verify code quality checks before committing changes, run the exact verification command for the task, inspect and copy the full output including the exit status, and report that evidence before stating anything has passed.

Can I use pre-release verification for CI checks and agent delegations?▼

Yes, you can use pre-release verification for CI checks and agent delegations by applying an evidence-first reporting pattern that requires running the full verification command and examining outputs before accepting agent-reported success or merging branches.

Why do my bug fixes fail CI checks after I declare them resolved?▼

Bug fixes fail CI checks after being declared resolved because of premature assertions without fresh verification evidence, requiring you to capture red flags, prevent rationalizations, and ensure reproducible proof like test outputs and build exit codes before claiming completion.