create-verify-test-coverage

Name: create-verify-test-coverage
Availability: InStock
Author: tsunami28

Measure line coverage and validate acceptance criteria tests before release.

Updated Jun 18, 2026

Search Tags:#code quality #testing #qa #acceptance criteria #test coverage #release readiness

Ready to run

npx skills add https://github.com/tsunami28/MindNova --skill create-verify-test-coverage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-verify-test-coverage
Source: https://github.com/tsunami28/MindNova/tree/main/.claude/skills/create-verify-test-coverage
Command: npx skills add https://github.com/tsunami28/MindNova --skill create-verify-test-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams determine whether a software change is adequately tested before release by measuring real coverage results and validating acceptance criteria coverage instead of relying on assumptions.

Core Features & Use Cases

Coverage Verification: Runs tests with coverage collection and reports measured line coverage for changed projects.
Acceptance Criteria Validation: Checks that numbered acceptance criteria have corresponding tests using the required story and AC trait mappings.
Release Readiness Checks: Helps QA workflows verify that changes are gate-ready before pull requests and deployments.

Quick Start

Use the create-verify-test-coverage skill to verify that the current story has sufficient test coverage and that all acceptance criteria are covered.

Frequently Asked Questions about create-verify-test-coverage

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

FAQPage Schema

How do I verify test coverage before releasing software changes?▼

To verify test coverage before release, you need to execute tests with coverage collection and measure line coverage for changed projects. This confirms your changes are adequately tested rather than relying on assumptions.

What is acceptance criteria validation in QA workflows?▼

Acceptance criteria validation checks that numbered acceptance criteria have corresponding tests using required story and AC trait mappings. It ensures every defined requirement is explicitly covered by automated tests before release.

How do I map acceptance criteria to tests for release readiness checks?▼

You map acceptance criteria to tests using required story and AC trait mappings. This trait-based mapping validates that each numbered acceptance criterion has a corresponding test, confirming quality gates are met.

Does test coverage verification work for pull request preparation?▼

Test coverage verification applies to pull request preparation by running tests with coverage collection and reporting measured line coverage for changed projects. It helps QA workflows verify changes are gate-ready before deployment.

When do I need to run acceptance criteria coverage checks?▼

You need to run acceptance criteria coverage checks during story verification, pull request preparation, and release readiness checks. This ensures software changes have adequate test coverage and validates acceptance criteria before deployment.

Why rely on measured coverage instead of assumptions for release readiness?▼

Relying on measured coverage instead of assumptions prevents untested changes from reaching production. By measuring real coverage results and validating acceptance criteria coverage, teams confirm quality gates are genuinely met before release.