verification-before-completion

Verify completion claims by executing commands and confirming exit codes.

Updated Aug 23, 2026

Search Tags:#verification #evidence #code-quality #verify #pull-requests #tests

Ready to run

npx skills add https://github.com/rapyuta-robotics/agent-ai --skill verification-before-completion-rapyuta-robotics

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces honest completion by requiring fresh verification evidence before any success claims.

Core Features & Use Cases

Verification steps: Define and execute a full verification command, read outputs, and confirm exit status before declaring success.
Evidence-based decisions: Prevent premature claims by validating results against explicit success criteria.
Use Case: Integrate into PR checks and CI pipelines to ensure changes are truly ready before merging.

Quick Start

Run your verification command, read the output, and only then declare 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 verify code changes before claiming completion in pull requests?▼

To verify code changes before claiming completion, execute a verification command, read the output, and confirm the exit status against success criteria to prevent premature success claims in pull requests.

What is evidence-based verification in CI pipelines?▼

Evidence-based verification in CI pipelines requires executing verification commands and reading fresh outputs to validate results against explicit success criteria before declaring a release ready.

How do I stop premature success claims during code reviews?▼

Stop premature success claims during code reviews by requiring fresh verification evidence, which means running tests, reading command outputs, and confirming exit codes before declaring a task complete.

Can I use verification checks for release readiness?▼

Yes, you can use verification checks for release readiness by integrating them into development cycles to ensure changes are validated against explicit success criteria before merging.

Do I need to run verification commands manually to prove completion?▼

Yes, you need to run verification commands manually or in a pipeline to prove completion, as the process requires reading fresh outputs and confirming exit codes before any success is declared.

What's the best way to ensure PR checks validate outcomes before merging?▼

The best way to ensure PR checks validate outcomes is to enforce honest completion by requiring execution of verification commands and confirming exit status before merging, preventing unverified success claims.