verify
Verify that a change really works before you claim completion
git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode /tmp/verify && cp -r /tmp/verify/skills/verify ~/.claude/skills/verifySKILL.md
# 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
Pre-planning consultant for requirements analysis (Opus)
Strategic Architecture & Debugging Advisor (Opus, READ-ONLY)
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Work plan and code review expert — thorough, structured, multi-perspective (Opus)
Root-cause analysis, regression isolation, stack trace analysis, build/compilation error resolution
UI/UX Designer-Developer for stunning interfaces (Sonnet)
External Documentation & Reference Specialist