verify

Verifies code changes against expected behavior using evidence-first testing and reporting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid overconfidence by turning “it seems to work” into verifiable evidence that a change truly passes the behavior you care about.

Core Features & Use Cases

  • Evidence-first verification: Focuses on confirming specific expected behaviors rather than vague completion claims.
  • Testing and narrowing strategy: Prioritizes existing tests, then typecheck/build, then narrow command checks, and finally manual validation if needed.
  • Transparent reporting: Summarizes what was verified, what commands/tests were run, what passed, and what failed or remains unverified.

Quick Start

Ask the AI to verify your change by identifying the exact expected behavior, running the narrowest relevant tests or checks available, and reporting only the confirmed 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 code change actually fixes the bug before merging?

Verifying a code change involves running an evidence-first sequence: existing tests, typecheck or build, narrow command checks, and manual validation to prove the specific behavior is fixed before marking the work complete.

What is the best way to confirm a refactor works without running the entire test suite?

The best way to confirm a refactor is applying a narrowing strategy: run targeted existing tests first, then typecheck and build, followed by narrow command checks to validate specific behaviors rather than executing broad, expensive test suites.

How do I report what remains unverified after running tests and typechecks?

Reporting what remains unverified requires transparent failure reporting that summarizes the commands run, what passed or failed, and explicitly discloses any behavior that lacks evidence or was not covered by the validation checks.

When do I need manual validation for a bug fix?

Manual validation is needed when existing tests, typecheck, build, and narrow command checks are unavailable or insufficient to prove the specific expected behavior your code change claims to address.

Does evidence-first verification work for feature development and refactoring?

Evidence-first verification applies to feature development, bug fixes, and refactoring by requiring verifiable evidence that a change passes the specific behaviors you care about before marking the work complete.