~verify

Verify change and experiment states against contract, diff, and evidence records.

5|2|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/Tx1207/hello-scholar --skill verify-tx1207
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ~verify
Source: https://github.com/Tx1207/hello-scholar/tree/main/skills/commands/verify
Command: npx skills add https://github.com/Tx1207/hello-scholar --skill verify-tx1207

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that the current change or experiment state satisfies contract, diff, change record and experiment evidence, ensuring deliverable readiness and traceability.

Core Features & Use Cases

  • End-to-end verification across plan packages, change records, and experiment data.
  • Checks that requirements, plan, tasks, diff, and evidence are aligned and complete.
  • Produces audit-ready notes and updates to relevant records for governance and review.

Quick Start

Invoke ~verify with a specific scope to start the validation and generate evidence of compliance.

Frequently Asked Questions about ~verify

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

FAQPage Schema
What is change record verification and how does it validate software changes?

Change record verification checks that current software changes satisfy contract, diff, and experiment evidence. It validates requirements coverage, plan alignment, tests, and evidence to ensure deliverable readiness and traceability for governance review.

How do I verify requirements coverage and plan alignment for an experiment package?

You verify requirements coverage by validating the experiment package against contract, diff, and evidence. This checks that requirements, plan, tasks, and evidence are aligned and complete, producing audit-ready notes for governance review.

Can I use contract and diff validation for both normal software changes and experiments?

Yes, contract and diff validation applies to normal software changes and experiments. It handles plan packages, change records, and experiment packages, checking requirements coverage, diffs, tests, and evidence to deliver verified outcomes.

What's the best way to generate audit-ready evidence for change records?

The best way to generate audit-ready evidence is to run end-to-end validation across plan packages, change records, and experiment data. This produces audit-ready notes and updates relevant records for governance and review.

Why does my experiment state fail validation against the change record?

Experiment state validation fails when requirements, plan, tasks, diff, and evidence are not aligned or complete. The validation checks these elements against the contract and change record to identify gaps in deliverable readiness.

Do I need a specific scope to start validation and generate compliance evidence?

Yes, you need to invoke validation with a specific scope to start the process and generate evidence of compliance. The scope determines whether it validates plan packages, change records, or experiment packages for verified outcomes.