verify

Verify code changes against promised behavior with evidence-backed checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents misleading “it works” assumptions by turning vague completion claims into concrete, checkable evidence.

Core Features & Use Cases

  • Verification-first workflow: Converts the requested change into an explicit set of behaviors to prove, then verifies them in a priority order.
  • Evidence-backed reporting: Summarizes exactly what was verified, including commands/tests run and clear pass/fail outcomes.
  • Manual fallback when automation can’t: When narrow automation is insufficient, it guides observable manual validation steps and records the resulting evidence.

Quick Start

Use the verify skill to validate a feature fix by running the narrowest relevant tests or build checks first, then performing direct command checks or manual validation if needed.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify code changes before claiming completion?

To verify code changes before completion, convert the requested change into an explicit set of behaviors to prove, then execute automated testing, typecheck, and build validation in a priority order to generate concrete evidence.

What is evidence reporting in build validation and testing?

Evidence reporting in build validation summarizes exactly what was verified, including the specific commands and tests executed, ensuring there are clear pass or fail outcomes rather than vague completion assumptions.

How do I confirm a bug fix or refactor safety without automated tests?

To confirm a bug fix or refactor safety without narrow automation, perform observable manual validation steps guided by the workflow, and record the resulting evidence to prove the behavior.

What is the best way to ensure refactoring does not break existing behavior?

The best way to ensure refactoring safety is to apply a verification-first workflow that runs the narrowest relevant tests and build checks first, followed by direct command checks if needed.

What happens to completion claims when verification checks fail?

When verification checks fail or remain unverified, the workflow prohibits any assertions of success, ensuring that completion claims are strictly backed by passing test and build validation evidence.

Can I use manual validation for feature validation when automation is insufficient?

Yes, when narrow automation is insufficient for feature validation, the workflow guides observable manual validation steps and records the resulting evidence to confirm the promised behavior.