verify

Verify functional changes with concrete evidence and explicit pass/fail results.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/xz1220/oh-my-kimi --skill verify-xz1220
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/xz1220/oh-my-kimi/tree/main/skills/verify
Command: npx skills add https://github.com/xz1220/oh-my-kimi --skill verify-xz1220

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you confirm that a change actually works by producing concrete evidence instead of vague claims.

Core Features & Use Cases

  • Evidence-first verification: Converts uncertain “it should run” statements into verifiable outcomes, including explicit pass/fail results.
  • Stepwise verification workflow: Tries existing tests first, then narrows to typecheck/build, then to focused commands, and finally provides manual or interactive validation steps when automation is insufficient.
  • No false completion: Refuses to report completion without real validation and clearly states what was verified versus what remains unverified.

Quick Start

Ask it to verify your specific claimed behavior and provide the exact proof requested, including which tests or commands it should run and what results it should report.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify a software fix actually works without relying on vague claims?

Software verification requires concrete evidence by executing tests and builds to produce pass/fail outcomes. It enforces an evidence-first workflow that enumerates validated items and explicitly states what remains unverified, refusing false completion.

How do I validate a code refactor when automated test coverage is incomplete?

Validating a code refactor with incomplete test coverage uses a stepwise workflow: run existing tests first, then narrow to typecheck and build commands, and finally provide manual validation steps when automation is insufficient to confirm behavior.

What is evidence-first verification in software engineering?

Evidence-first verification is a mechanism requiring concrete proof for functional changes. It enumerates validated items, commands executed, and pass/fail status, explicitly stating what remains unverified to prevent false completion claims.

Can I use typecheck and build commands to confirm a functional change?

Yes, you can use typecheck and build commands to confirm a functional change. They serve as secondary validation steps when existing tests are insufficient, providing automated confidence before manual validation is required.

What are the limitations of automated verification for regression testing?

Automated verification for regression testing may be insufficient when test coverage is incomplete. It cannot confirm all functional changes automatically, requiring manual or interactive validation steps to explicitly state what remains unverified.