write-tests

Generates tests for production files through an inventory-first pipeline with executable coverage gates and adversarial review.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill write-tests-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-tests
Source: https://github.com/greglas75/zuvo/tree/main/skills/write-tests
Command: npx skills add https://github.com/greglas75/zuvo --skill write-tests-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Writing tests for existing production code often produces shallow suites with tautological assertions, missed branches, and unverified coverage claims. This Skill enforces a disciplined single-file pipeline that freezes the public surface inventory before writing, proves coverage with an executable gate script, and subjects every suite to blind coverage audit and adversarial review. ## Core Features & Use Cases - Inventory-first pipeline: Classifies each production file by code type, complexity, and testability, then freezes a coverage manifest before any test is written. - Executable coverage gate: Uses scripts/test-coverage-gate.py to scaffold, validate, and audit coverage rather than trusting self-reported claims. - Independent review agents: Dispatches blind coverage auditors, adversarial test reviewers, and a Q1-Q25 quality reviewer for evidence-based scoring. - Use Case: Point it at an uncovered TypeScript service file; it analyzes the code, builds a frozen test contract, writes behavioral tests, runs the suite, and iterates until the coverage gate and reviewers pass. ## Quick Start Ask the AI to run the write-tests skill on a specific production file, or use auto mode to discover and test all uncovered files one at a time.

Frequently Asked Questions about write-tests

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

FAQPage Schema
How do I write tests for existing production code automatically?

Run the write-tests skill with a file path, directory, or auto mode. It classifies the code, freezes a coverage inventory before writing, generates behavioral tests, then verifies them with an executable coverage gate and independent reviewer agents.

What test frameworks does this test generation pipeline support?

It detects vitest, jest, pytest, and phpunit from project manifests and config files. Stack-specific rules load for JavaScript, TypeScript, Python, and PHP, and runner-by-extension tables in repo ADRs are treated as binding.

Can I preview the test plan without writing any tests?

Yes, use the --dry-run flag. It runs the bootstrap and analysis phases for all target files, prints the classification table and plan, then stops without executing any suite-mutating commands.

How does the coverage gate verify test completeness?

The scripts/test-coverage-gate.py tool scaffolds a manifest of every public symbol and boundary at coverage NONE, then validates that each row has test evidence. The writer's own claims are never accepted as proof of coverage.

What happens when the test review infrastructure is unavailable?

A reviewer preflight runs before any test is written. If providers fail, the run is marked DRAFT/BLOCKED_INFRA: tests may still be written for standalone value, but no file can be reported as PASS.

When should I not use this test writing skill?

It is scoped to existing production files with missing or partial coverage. For new feature tests use the build skill, for mass anti-pattern repair use fix-tests, and for audit-only passes use test-audit.