gvm-test

Verify completed builds with acceptance tests and requirement coverage audits.

5|Updated May 4, 2026
One-click install
npx skills add https://github.com/gerquinn1978/gvm --skill gvm-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gvm-test
Source: https://github.com/gerquinn1978/gvm/tree/main/grounded-vibe-methodology/skills/gvm-test
Command: npx skills add https://github.com/gerquinn1978/gvm --skill gvm-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gvm-code-review, gvm-test-cases, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill verifies that completed builds are functional and meet the required standards, ensuring that the product works as intended.

Core Features & Use Cases

  • Build Verification: Verify the completeness and functionality of a build.
  • Integration Seam Audit: Check for issues between integrated components.
  • Acceptance Test Verification: Run predefined tests to ensure the build meets requirements.
  • Smoke Testing: Perform a basic check to ensure the product works as expected.
  • Requirement Coverage Audit: Ensure all requirements are met.
  • Verdict: Provide a final assessment of the build's readiness.

Quick Start

Run the gvm-test skill to verify the build. Example: /gvm-test

Frequently Asked Questions about gvm-test

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

FAQPage Schema
How do I verify completed software builds and ensure product functionality?

Build verification is performed by running prerequisite checks, integration seam audits, acceptance tests, smoke testing, and requirement coverage audits to ensure product functionality. This structured workflow provides a final verdict on build readiness.

How do I run an integration seam audit on my software build?

An integration seam audit checks for issues between integrated components within a completed build. It is executed as part of a structured verification workflow alongside prerequisite checks and acceptance tests to ensure integrated software functions correctly.

Do I need code review and test cases before running build verification?

Yes, build verification requires a completed build, a code review report, and predefined test cases. It depends on the gvm-code-review and gvm-test-cases outputs to perform prerequisite checks and requirement coverage audits effectively.

What is the best way to perform smoke testing and acceptance tests together?

The best way to perform smoke testing and acceptance tests together is through a structured verification workflow. This approach executes basic functionality checks and predefined tests sequentially to provide a final readiness assessment.

When do I need a requirement coverage audit for software testing?

A requirement coverage audit is needed during software testing to ensure all project requirements are met by the completed build. It is performed as a final step in the verification workflow before delivering a build readiness verdict.

Why does build verification require prerequisite checks before acceptance testing?

Build verification requires prerequisite checks to validate the presence of a completed build, code review report, and test cases. These checks ensure the environment is ready before attempting acceptance testing and integration seam audits.