verification-before-completion

Run verification commands and report evidence before claiming completion.

15|2|Updated Feb 12, 2026

Search Tags:#testing #qa #verification #completion #build #evidence #ci

Ready to run

npx skills add https://github.com/kousukef/forge --skill verification-before-completion-kousukef

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification is dishonesty, not efficiency. This rule enforces that evidence must be produced and verified before any completion claim; only after fresh verification can a claim be made.

Core Features & Use Cases

Formal verification workflow: Identify the command or evidence needed, run it freshly, read full output and exit codes, verify results, and only then claim success.
Guardrails against premature closure: highlights red flags and rationalization prevention to prevent deceptive completion claims.
Applicable to: unit tests, integration tests, linting, builds, and agent-driven tasks that must be validated before deployment or PRs.

Quick Start

Run the verification command and review the output before making any completion claim.

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 claiming a build is complete without running verification?▼

Verification before completion requires running the relevant test or build command, capturing fresh evidence like output and exit codes, and checking the actual results before making any success claim. This workflow eliminates premature closure on unit tests, integration tests, linting, and builds.

What is the best way to verify build evidence before merging a pull request?▼

The best way to verify build evidence is to execute the verification command, capture the full output and exit codes, and validate the actual results before claiming completion. This formal workflow prevents rationalization and ensures only validated work reaches deployment or pull requests.

Why does CI verification fail when tests are not run freshly before completion?▼

Verification fails when completion is claimed without fresh evidence because it bypasses the required validation workflow. Guardrails against premature closure highlight red flags and prevent rationalization, ensuring that unit tests, integration tests, and builds are actually run and validated before any success claim.

How to enforce QA testing evidence before claiming task completion?▼

To enforce QA testing evidence, state exactly what proves completion, run the verification command freshly, and report the actual results with evidence. This workflow applies to unit tests, integration tests, linting, and agent-driven tasks, preventing premature closure and unverified claims.

When do I need to run verification commands before claiming success?▼

You need to run verification commands before claiming success for any task requiring validation, such as unit tests, integration tests, linting, or builds. The workflow demands fresh verification evidence, reading full output and exit codes, and confirming actual results before any completion claim.