wv-verify-complete

Select and run the strongest verification method, then record evidence in node metadata.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/AGM1968/weave --skill wv-verify-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wv-verify-complete
Source: https://github.com/AGM1968/weave/tree/main/.claude/skills/wv-verify-complete
Command: npx skills add https://github.com/AGM1968/weave --skill wv-verify-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that task closures are backed by verifiable evidence rather than optimistic assumptions, reducing the risk of post-closure rework.

Core Features & Use Cases

  • Guidance on selecting the strongest applicable verification method (test, build, typecheck, lint, runtime, or diff) and running the appropriate commands for the project type.
  • Evidence capture and attachment to node metadata for auditability and traceability.
  • Pre-close gating that blocks wv done until verification succeeds, with clear escalation paths for deferred verification when necessary.

Quick Start

Run the verification flow by invoking the appropriate command to attach evidence and gate completion.

Frequently Asked Questions about wv-verify-complete

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

FAQPage Schema
How do I enforce verifiable completion before closing tasks?

Verifiable completion requires selecting the strongest applicable verification method—such as test, build, typecheck, or lint—and running the commands to ensure evidence passes before closing a task.

What verification methods can I use to gate task closure?

Verification methods include test, build, typecheck, lint, runtime, and diff. The system identifies the strongest applicable approach for your project type and runs the corresponding commands to confirm success.

How do I capture evidence for quality-assurance workflows?

Evidence capture records verification results—method, command, result, evidence, and verified timestamp—directly into node metadata, ensuring full auditability and traceability for quality-assurance workflows.

Can I defer verification when a pre-close gate blocks task closure?

Yes, when the pre-close gate blocks task closure, clear escalation paths exist to handle deferred verification, allowing you to proceed when immediate verification is not feasible.

Does this verification approach work with any project type?

The approach adapts to your project type by identifying the strongest applicable verification method and running the appropriate commands within your environment to validate completion.