verify

Verify software changes through tests, typecheck, and manual validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kamelmh/opencode --skill verify-kamelmh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/kamelmh/opencode/tree/main/skills/verify
Command: npx skills add https://github.com/kamelmh/opencode --skill verify-kamelmh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents false confidence by turning vague claims like “it should work” into concrete, checkable evidence.

Core Features & Use Cases

  • Evidence-first verification: Turns the expected behavior into specific things to prove before declaring completion.
  • Verification order that prioritizes safety: Starts with existing tests, then typecheck/build, then narrow command checks, and finally manual validation when automation is insufficient.
  • Transparent reporting: Summarizes what passed, what failed, and what remains unverified without bluffing.

Quick Start

Use the verify skill to validate a proposed fix by asking it to identify the exact behavior that must be proven and then run the narrowest available tests or commands, reporting clear pass/fail results.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify a bug fix works before declaring completion?

To verify a bug fix, you must provide concrete evidence that the change works by running existing tests, performing typecheck/build, executing narrow command checks, and finally applying manual validation with explicit pass/fail reporting.

What is evidence-first verification for software refactoring?

Evidence-first verification for refactoring turns vague claims like "it should work" into checkable proof by prioritizing existing tests, typecheck/build, narrow command checks, and manual validation to demonstrate correctness before completion.

How do I prove a proposed software change works without bluffing?

You prove a proposed software change works through transparent reporting that summarizes what passed, what failed, and what remains unverified, relying on an evidence-first workflow instead of unvalidated claims.

Does this verification approach work for feature work and bug fixes?

Yes, this verification approach applies to feature work, bug fixes, and refactors where correctness must be demonstrated before completion, applying an evidence-first workflow that prioritizes existing tests and typecheck/build.

What order should I run tests and checks to verify a refactor?

To verify a refactor, follow a safety-prioritized verification order: start with existing tests, then typecheck/build, then narrow command checks, and finally manual validation when automation is insufficient.

How do I report CI confidence for unverified changes safely?

You report CI confidence safely by summarizing what passed, what failed, and what remains unverified without bluffing, ensuring transparent evidence reporting instead of relying on unvalidated claims for completion.