Agent Skills
› evolution-foundation/evo-nexus
› dev-verify
dev-verify
GitHub用于在功能、修复或重构后验证变更是否有效，将模糊声明转化为具体证据。优先使用现有测试，其次构建检查，最后手动验证，确保交付物有据可查。
Trigger Scenarios
用户希望确认代码修改是否生效
提交完成前需要验证证据
Install
npx skills add evolution-foundation/evo-nexus --skill dev-verify -g -y
SKILL.md
Frontmatter
{
"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
- Identify the exact behavior that must be proven.
- Prefer existing tests first.
- If coverage is missing, run the narrowest direct verification commands available.
- If direct automation is not enough, describe the manual validation steps and gather concrete observable evidence.
- Report only what was actually verified.
Verification order
- Existing tests
- Typecheck / build
- Narrow direct command checks
- 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.
Version History
- 7f5dd76 Current 2026-07-25 04:53
