verify-coverage

Verify ticket acceptance criteria have passing tests and 100% coverage.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill verify-coverage-nand1234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-coverage
Source: https://github.com/nand1234/Agentic-workflow-builder/tree/main/ai-dev-worflow/.claude/skills/verify-coverage
Command: npx skills add https://github.com/nand1234/Agentic-workflow-builder --skill verify-coverage-nand1234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that all acceptance criteria for a ticket have passing tests and 100% coverage, ensuring quality gates before merging.

Core Features & Use Cases

  • Validates mapping between ticket requirements and unit tests by reading docs/requirements files.
  • Executes the verification flow to confirm that every acceptance criterion has a corresponding test and full coverage.
  • Generates a verification report that clearly states pass/fail status and recommended fixes.

Quick Start

Provide a TICKET-ID and feature slug to verify that all acceptance criteria have passing tests and 100% coverage.

Frequently Asked Questions about verify-coverage

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

FAQPage Schema
How do I verify ticket acceptance criteria have passing tests before merging?

To verify ticket acceptance criteria, you provide a TICKET-ID and feature slug so the system reads the requirement traceability matrix, executes mapped tests, and computes 100% coverage. It outputs a verification report confirming pass or fail status.

What is a requirements traceability matrix for QA coverage?

A requirements traceability matrix for QA coverage maps ticket acceptance criteria to specific unit tests. This Skill parses a markdown RTM file to ensure every requirement has a corresponding passing test before computing overall coverage.

How do I check if all ticket tests pass across multiple repositories?

You can check if all ticket tests pass across multiple repositories by supplying the TICKET-ID and feature slug. The system reads the corresponding docs and test mappings to execute tests and generate a unified verification report.

Does this QA coverage verification work with existing markdown documentation?

Yes, this QA coverage verification works with existing markdown documentation by reading files formatted as docs/requirements/$FEATURE-rtm.md. It parses these files to map acceptance criteria to your existing tests.

What happens when a ticket acceptance criterion does not have 100% test coverage?

When a ticket acceptance criterion does not have 100% test coverage, the verification report clearly states the fail status and provides recommended fixes to address the missing tests before merge-to-cp.