Verification Before Completion

Run verification commands and report exit codes before completion claims.

8|1|Updated Apr 15, 2026

Search Tags:#testing #verification #completion #evidence #quality-assurance #ci #audit-trail

Ready to run

npx skills add https://github.com/gujiachun-rainbow/RainClaw --skill verification-before-completion-gujiachun-rainbow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Verification Before Completion
Source: https://github.com/gujiachun-rainbow/RainClaw/tree/main/.trae/skills/verification-before-completion
Command: npx skills add https://github.com/gujiachun-rainbow/RainClaw --skill verification-before-completion-gujiachun-rainbow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work without verification is risky; this rule ensures that any claim of completion is backed by fresh, verifiable evidence.

Core Features & Use Cases

Enforces running a verification command before marking completion
Captures full command output and exit status for audit trails
Provides a clear, repeatable gate for CI or manual checks

Quick Start

Run the verification gate on your current project to confirm all checks pass.

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 evidence-based completion checks before claiming a build is finished?▼

Evidence-based completion requires running a planned verification command to capture full output and evaluate exit codes before marking a task finished. This approach ensures any claim of completion is backed by fresh, verifiable outputs from CI or test suites.

What is the best way to capture CI output and exit codes for an audit trail?▼

Capturing CI output for an audit trail involves executing a verification command that records full output and exit status. This creates a clear, repeatable gate ensuring that builds, tests, or releases are backed by verifiable evidence.

Can I use this verification gate for manual checks outside of CI pipelines?▼

Yes, this verification gate applies across software development workflows, functioning as a clear, repeatable check for both CI pipelines and manual reviews. It enforces running a planned command and reporting results with evidence before completion.

How do I verify test suite results and lint checks before marking a release complete?▼

To verify test suite results and lint checks, run a planned verification command that evaluates exit codes and captures full output. This enforces strict procedural requirements, ensuring completion claims are backed by fresh verifiable evidence.

Why does claiming work without verification cause problems in software development?▼

Claiming work without verification is risky because it allows completion claims without fresh, verifiable evidence. Enforcing an evidence-based completion check mitigates this by requiring test suites, lint checks, and CI outputs to pass before finalizing.

What are the limitations of relying on manual verification for completion claims?▼

Manual verification lacks a repeatable gate and automated audit trail, making it prone to skipping checks. A strict procedural rule requiring fresh command execution, output capture, and exit code evaluation provides consistent evidence-based completion.