/dev-verify
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.
$ npx -y skills add evolution-foundation/evo-nexus --skill dev-verify --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/dev-verify
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
dev-verify.SKILL.mdname: 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`.
Read more
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`.
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill