coverage-guard

Name: coverage-guard
Availability: InStock
Author: Vertexcover

Enforce minimum unit test coverage for tarash-gateway using coverage.json.

4|Updated Jan 1, 2026

Search Tags:#pytest #unit-test #coverage #orchestrate #test-automation #tarash-gateway

Ready to run

npx skills add https://github.com/vertexcover-io/tarash --skill coverage-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coverage-guard
Source: https://github.com/vertexcover-io/tarash/tree/main/.claude/skills/coverage-guard
Command: npx skills add https://github.com/vertexcover-io/tarash --skill coverage-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a minimum unit test coverage threshold for tarash-gateway, automatically generating a coverage-gap spec and handing off to the orchestrate workflow when coverage falls short.

Core Features & Use Cases

Load the testing skill to align on test conventions.
Run the coverage analysis and parse coverage.json to determine overall and per-file coverage.
Generate a Coverage Gap Spec and trigger the orchestrate workflow for automated test creation when coverage is insufficient.
Provide a clear PASS/FAIL summary and actionable gaps for developers.

Quick Start

Run the coverage guard to verify unit test coverage and generate a gap spec when coverage falls below the threshold.

Frequently Asked Questions about coverage-guard

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

FAQPage Schema

How do I enforce a minimum pytest unit test coverage threshold automatically?▼

To enforce pytest unit test coverage, the skill evaluates overall and per-file coverage against a configurable THRESHOLD constant after code changes. If coverage falls short, it generates a Coverage Gap Spec and triggers the orchestrate workflow for automated test generation.

How does automated test generation work when unit test coverage is insufficient?▼

Automated test generation triggers when coverage is insufficient by creating a Coverage Gap Spec from the coverage.json report. This spec is passed to the orchestrate workflow, which then handles the automated creation of missing unit tests.

Can I use this coverage guard to identify per-file test coverage gaps in my repository?▼

Yes, you can use this coverage guard to identify per-file test coverage gaps. It runs the coverage analysis command, parses the resulting coverage.json report, and provides a clear PASS/FAIL summary with actionable gaps for developers.

What's the best way to orchestrate test automation after detecting a coverage gap?▼

The best way to orchestrate test automation after detecting a coverage gap is to generate a Coverage Gap Spec and pass it to the orchestrate workflow. This automatically initiates the creation of missing unit tests to meet the threshold.

Do I need a coverage.json report to trigger automated test orchestration?▼

Yes, you need a coverage.json report to trigger automated test orchestration. The skill relies on this file to detect coverage gaps across the repository and determine whether the measured coverage meets the configured threshold.

Why does my unit test coverage check fail and trigger the orchestrate workflow?▼

Your unit test coverage check fails and triggers the orchestrate workflow because the parsed coverage.json report indicates that the overall coverage is below the configured THRESHOLD constant, requiring automated test generation.