# Verify

Verify that a change really works before you claim completion

- Repository: https://github.com/Yeachan-Heo/oh-my-claudecode (40492 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -g -a claude-code -y`
Codex: `npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -g -a codex -y`
Cursor: `npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -g -a cursor -y`
Gemini CLI: `npx skills add Yeachan-Heo/oh-my-claudecode --skill verify -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Yeachan-Heo/oh-my-claudecode`

## Description

Verify that a change really works before you claim completion

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Verify

Use this skill when the user wants confidence that a feature, fix, or refactor actually works.

## Goal
Turn vague “it should work” claims into concrete evidence.

## Workflow
1. Identify the exact behavior that must be proven.
2. Prefer existing tests first.
3. If coverage is missing, run the narrowest direct verification commands available.
4. If direct automation is not enough, describe the manual validation steps and gather concrete observable evidence.
5. Report only what was actually verified.

## Verification order
1. Existing tests
2. Typecheck / build
3. Narrow direct command checks
4. Manual or interactive validation

## Rules
- Do not say a change is complete without evidence.
- If a check fails, include the failure clearly.
- If no realistic verification path exists, say that explicitly instead of bluffing.
- Prefer concise evidence summaries over noisy logs.

## Output
- What was verified
- Which commands/tests were run
- What passed
- What failed or remains unverified