verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: abzhaw

Run verification commands and require explicit confirmation before claiming completion.

Updated Feb 21, 2026

Search Tags:#verification #completion #evidence #pr #guardrails #tests #claim

Ready to run

npx skills add https://github.com/abzhaw/juliaz_agents --skill verification-before-completion-abzhaw

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that work is verifiably complete by requiring evidence and verification before any completion claims, committing, or PRs.

Core Features & Use Cases

Enforces a strict verification flow: IDENTIFY, RUN, READ, VERIFY, and ONLY THEN claim.
Applies across code changes, tests, linting, builds, and deployment gates to prevent premature status updates.
Use case: before merging a feature branch, run the verification sequence to confirm tests pass and outputs align with expectations.

Quick Start

Run the verification command, review the full output, and only claim success if the results prove the 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 enforce verification checks before claiming code completion in PR workflows?▼

To enforce verification before completion claims, apply a strict sequence: IDENTIFY the task, RUN the full verification command, READ the output, and VERIFY exit codes before updating status. This prevents premature completion claims across PR workflows.

What is the step-by-step process to verify tests and linting before merging a feature branch?▼

The verification process requires calling the full verification command, parsing exit codes, and requiring explicit confirmation before updating status. You run the sequence, review the full output, and only claim success if results prove the claim.

Can I use this verification pattern across deployment gates and release workflows?▼

Yes, this verification pattern applies across code changes, tests, linting, builds, and policy enforcement for deployment gates and release workflows. It ensures outputs align with expectations before any status is updated.

Does this approach require any specific testing frameworks or dependencies to run?▼

No dependencies are required. The approach functions as an advanced internal reasoning pattern that parses exit codes from your existing verification commands, requiring explicit confirmation before allowing any completion claims.

Why does my completion status update before build and test verification finishes?▼

Completion status updates prematurely when evidence and verification are not enforced. Implementing a guardrail that parses exit codes and demands explicit confirmation prevents status changes until tests, linting, builds are proven successful.