verification-before-completion

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

Run verification commands and analyze output before reporting task completion.

Updated Apr 18, 2026

Search Tags:#workflow #testing #tdd #quality assurance #verification #agent reliability

Ready to run

npx skills add https://github.com/NeuralChainX/Superpowers --skill verification-before-completion-neuralchainx

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common issue of AI agents claiming tasks are finished without actually verifying the results, which leads to broken code, missed requirements, and loss of trust.

Core Features & Use Cases

Verification Gatekeeping: Forces the agent to execute specific verification commands before declaring any work complete.
Evidence-Based Reporting: Ensures that every claim of success is backed by concrete output (e.g., test results, exit codes, or diffs).
Use Case: Before submitting a pull request, the agent must run the full test suite and confirm zero failures, rather than assuming the code works based on partial checks.

Quick Start

Instruct the agent to verify the current task by running the appropriate test suite and confirming the output before reporting 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 stop an AI agent from claiming a task is complete without running tests?▼

To stop false completion claims, you need verification gatekeeping that forces the agent to execute specific test commands and analyze their output before reporting success. This enforces evidence-based assertions by requiring concrete exit codes or test results.

What is evidence-based work completion in software development?▼

Evidence-based work completion is a verification protocol requiring objective analysis of command outputs like test results and diffs before declaring a task done. It prevents agents from assuming code works based on partial checks by demanding concrete proof.

How do I ensure my pull request passes the full test suite before submission?▼

To ensure pull request quality, enforce a verification protocol that runs the full test suite and confirms zero failures before submission. This requires the agent to execute testing commands and analyze the output for evidence-based reporting.

Does this verification approach work with linting and bug fixing workflows?▼

Yes, this verification approach applies to software development workflows including linting, building, and bug fixing. It requires executing specific verification commands for each task type and objectively analyzing their output to ensure reliability.

Why does my agent report success but the code is still broken?▼

Agents report false success when they lack verification gatekeeping, leading to broken code. Enforcing evidence-based completion prevents this by requiring the execution of specific verification commands and objective analysis of their output before claiming success.