verification-before-completion

Run full verification commands and report evidence before claiming completion.

1|Updated Feb 22, 2026

Search Tags:#verification #quality-assurance #code-review #build-verification #workflow-guardrails #completion-claims

Ready to run

npx skills add https://github.com/1337hero/claude-toolkit --skill verification-before-completion-1337hero

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/1337hero/claude-toolkit/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/1337hero/claude-toolkit --skill verification-before-completion-1337hero

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claims of completion often lack verified evidence, risking dishonesty and rework. This skill enforces a discipline where every completion claim is backed by fresh verification results.

Core Features & Use Cases

Enforces a step-by-step gate: identify command, run full verification, read outputs, verify evidence, and only then claim success.
Applicable to code commits, builds, tests, and PR readiness across software projects.
Provides a clear, auditable protocol to prevent premature or dishonest completion claims.

Quick Start

Run the full verification command and report the exact results before claiming completion.

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 build verification before a pull request is marked as complete?▼

To enforce build verification before a pull request is marked complete, you must run the full verification command, parse the outputs, count any failures, and report the exact results before making any success claims.

What is the best way to prevent premature code completion claims in automated pipelines?▼

The best way to prevent premature code completion claims in automated pipelines is enforcing a step-by-step gate that requires fresh verification evidence, ensuring every success statement is backed by auditable test results.

How does verification evidence ensure quality assurance during code commits?▼

Verification evidence ensures quality assurance during code commits by requiring developers to run full verification commands and review outputs, providing an auditable protocol that prevents dishonest or unverified completion claims.

Can I use workflow guardrails to verify test outputs across software projects?▼

Yes, you can use workflow guardrails to verify test outputs across software projects by applying a strict protocol that identifies the command, runs full verification, reads outputs, and reports status with evidence before completion.

Why does claiming code review completion without fresh verification cause rework?▼

Claiming code review completion without fresh verification causes rework because lacking verified evidence risks dishonesty, whereas enforcing verification gates ensures success statements are always backed by actual test and build results.

Do I need to parse build outputs to guarantee PR readiness?▼

Yes, you need to parse build outputs to guarantee PR readiness, as the verification protocol requires counting failures and reporting exact results to provide evidence before any pull request success claims are made.