verification

Enforces timestamped proof-of-evidence before allowing task completion across workflows.

Updated Mar 22, 2026

Search Tags:#automation #verification #evidence #quality-assurance #guardrails #timestamp

Ready to run

npx skills add https://github.com/shusuke-ioku/r2 --skill verification-shusuke-ioku

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/shusuke-ioku/r2/tree/main/src/r2/template/.claude/skills/verification
Command: npx skills add https://github.com/shusuke-ioku/r2 --skill verification-shusuke-ioku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces that any claim of task completion—whether code changes, analysis outputs, or manuscript updates—must be backed by fresh, timestamped evidence before it is reported as done.

Core Features & Use Cases

Timestamped gates ensure evidence is produced before declaring completion.
Multi-workflow applicability covers software, data analyses, and document workflows to prevent premature claims.
Guardrail orchestration integrates with scripts, outputs, and manuscripts to maintain traceable accountability.

Quick Start

After completing a task, run the verification gate to generate and attach timestamped evidence.

Frequently Asked Questions about verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I require timestamped proof before confirming task completion?▼

To require timestamped proof for task completion, you need guardrails that enforce running verification commands and presenting evidence like test results, compiled outputs, or diff reports before any changes are reported as done.

What is timestamped evidence in quality assurance workflows?▼

Timestamped evidence in quality assurance is fresh proof generated by running verification commands, such as test results or diff reports, produced before declaring a task complete to prevent premature claims across software, data analyses, and document workflows.

How do I prevent premature claims of task completion in software engineering?▼

You prevent premature claims of task completion by implementing guardrails that require running verification commands and attaching timestamped evidence, ensuring no task is reported as done without fresh proof.

Can I use verification guardrails for data analyses and document workflows?▼

Yes, verification guardrails apply across software scripts, data analyses, and document workflows, enforcing that timestamped evidence like compiled outputs or diff reports is produced before any task completion is confirmed.

What's the best way to automate evidence generation for task completion?▼

The best way to automate evidence generation is using a verification gate that orchestrates guardrails, requiring running verification commands to produce timestamped evidence such as test results and diff reports before reporting completion.

Why does my task completion claim need timestamped proof?▼

Task completion claims need timestamped proof to ensure traceable accountability, preventing premature claims by requiring fresh evidence like test results, compiled outputs, or diff reports before any changes are reported as done.