dev-verify

Enforce fresh runtime evidence before declaring code completion.

19|5|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/edwinhu/workflows --skill dev-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-verify
Source: https://github.com/edwinhu/workflows/tree/main/lib/skills/dev-verify
Command: npx skills add https://github.com/edwinhu/workflows --skill dev-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the premature declaration of task completion by enforcing rigorous, fresh verification of code execution and output, ensuring that features truly work as intended before being presented as finished.

Core Features & Use Cases

  • Mandatory Fresh Evidence: Guarantees that all claims of completion are backed by recent, independently executed command outputs.
  • E2E Verification: Emphasizes the necessity of end-to-end tests for user-facing features, deeming unit tests insufficient on their own.
  • Use Case: Before merging a new feature, this Skill ensures that all automated tests pass, the build succeeds, and any user-facing changes are confirmed through end-to-end simulations, preventing the release of untested or partially functional code.

Quick Start

Run the dev-verify skill to confirm that all automated tests pass and the build is successful.

Frequently Asked Questions about dev-verify

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

FAQPage Schema
How do I enforce code verification before claiming task completion?

Code verification before completion requires mandating fresh runtime evidence from independently executed commands, ensuring features function properly before being marked as finished to prevent user-discovered failures.

Why are unit tests insufficient for verifying user-facing features?

Unit tests alone are insufficient for user-facing features because end-to-end testing is required to simulate user interactions and confirm the entire workflow operates correctly across integrated system components.

What is the best way to prevent premature code completion claims in CI/CD?

The best way to prevent premature completion claims in CI/CD is implementing a strict gate function that identifies, runs, reads, and verifies command outputs, demanding fresh execution evidence before merging.

How do I verify automated tests pass before merging a new feature?

To verify automated tests pass before merging, execute a mandatory verification process that runs the build, collects recent command outputs, and confirms end-to-end simulations succeed alongside unit tests.

Does end-to-end testing require fresh runtime evidence for every build?

End-to-end testing requires fresh runtime evidence for every build to guarantee that all completion claims are backed by recently executed outputs, preventing the release of partially functional or untested code.

What limitations exist when relying solely on build success for quality assurance?

Relying solely on build success limits quality assurance because it does not provide fresh runtime evidence of user-facing behavior, necessitating end-to-end test execution to truly verify features work as intended.