dev-verify

What it does and when to use it

Verify that a change really works before claiming completion. Use when the user wants confidence that a feature, fix, or refactor actually works — turns vague "it should work" claims into concrete evidence. Pairs with @oath-verifier agent.

Triggers from the description

How it works

1. Goal
2. Workflow
3. Verification order
4. Rules
5. Output
6. When to delegate

---
name: dev-verify
description: Verify that a change really works before claiming completion. Use when the user wants confidence that a feature, fix, or refactor actually works — turns vague "it should work" claims into concrete evidence. Pairs with @oath-verifier agent.
---

# Dev Verify

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

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

## When to delegate
For deeper verification with formal acceptance criteria mapping, delegate to `@oath-verifier`.

Versions

Database snapshot: 13.11.2026 · package version 8a861b6c04e6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 90verify
  Prove that a change actually works by running the project's checks and reporting the evidence. Use after implementing anything, when the user asks whether a change works, or before declaring a task done.
• 90evidence-over-claims
  当用户需要验证 Bug 是否真的被修复、功能是否真正完成、或性能优化是否有效时调用此 skill。适用于 Bug 修复验证、功能完成确认、性能优化验证。不适用于：纯理论讨论、未实现的计划、无法量化的主观判断。关键 trigger 信号："verify"、"ensure fixed"、"actually works"、"evidence"、"proof"、"test passed"、"benchmark"。
• 95hardproof
  Prove coding work before calling it done. Use when the user asks to implement, fix, refactor, migrate, or verify a change and wants evidence, or when the user invokes hardproof. Freezes acceptance checks, runs a read-only independent verifier, and blocks "done" until a gate…
• 100verification
  Verify that code actually works before claiming it does. Use when writing or reviewing tests, validating a fix, benchmarking or profiling, debugging silent failures, or reporting completion status. Applies to any language, engine, or framework.
• 100verify-pr-fix
  Manually verify that a bug-fix PR actually works by reproducing the failure before the fix and confirming it is gone after, with captured evidence, then posting findings to the PR (and optionally the linked issue). Use when asked to manually verify a PR/fix, reproduce an issue…
• 100verify-the-result
  Procedure for confirming that work actually succeeded before calling it done. Use it after any write, data move, deploy, fix or test run, and whenever a tool, script or log reports success.