skills.rest
EvolutionAPI
EvolutionAPIOFFICIAL
Explore all skills by this author →
GitHub

dev-verify

Verify development changes and report evidence of passed and failed checks.

520|175|Updated Apr 8, 2026
Search Tags:#testing#evidence#quality-assurance#verify#acceptance#code-change#feature-validation
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-verify-evolutionapi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-verify
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/dev-verify
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-verify-evolutionapi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn vague "it should work" claims into concrete evidence by providing a verifiable trail that a change actually works.

Core Features & Use Cases

  • Evidence-based validation: Prefer existing tests, then perform targeted checks when coverage is missing.
  • Concise verification reports: Summarizes what was verified, what passed, and what remains unverified.
  • Integration with oath-verifier: Pairs with dedicated agents for formal acceptance criteria.

Quick Start

Start the verification on the target change to generate a concrete evidence report.

Frequently Asked Questions about dev-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a code change with concrete evidence instead of just assuming it works?▼

Feature validation involves identifying the exact behavior to prove and collecting observable proof through existing tests or direct checks. It turns vague assumptions into a concise report detailing what passed, failed, and remains unverified.

What is the best way to generate an evidence-based verification report for a refactor?▼

The best way to generate an evidence report for a refactor is to apply targeted checks when test coverage is missing. This produces a concise summary detailing exactly what was verified, what passed, what failed, and what remains unverified.

How do I validate a bug fix when my existing test coverage is incomplete?▼

To validate a bug fix with incomplete test coverage, you prefer existing tests first, then perform targeted direct checks for missing coverage. This yields a concise report detailing what passed, failed, and remains unverified.

Can I use formal acceptance criteria integration for my feature validation workflow?▼

Yes, feature validation can integrate with formal acceptance criteria by pairing with dedicated agents. This ensures changes across development tasks are backed by a verifiable trail of concrete evidence.

Related Skills

Explore More Software Engineering Skills→
HuytutuHuytutu

test-driven-development

Enforce test-first development with RED-GREEN-REFACTOR cycles and bug fix patterns.

Community
Intermediate
ArabelaTsoArabelaTso
142

verification-boundary-reporter

Analyze Isabelle, Coq, and Dafny artifacts to report verified and unverified components.

Community
Advanced
zebbernzebbern
5

code-review

Generates structured code-review checklists and validates acceptance criteria with traceable evidence.

Community
Advanced
elophantoelophanto
116

verification-before-completion

Execute verification commands and report pass/fail with evidence before completion.

Community
Advanced