quality-test-gen

Generate parallel unit, integration, and e2e test suites from a CSV of source files.

511|63|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/catlog22/Maestro-Flow --skill quality-test-gen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-test-gen
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/quality-test-gen
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill quality-test-gen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates tests at scale by decomposing a codebase into independent test-generation agents driven by a CSV wave pipeline, replacing slow manual test writing and improving coverage discovery and reporting.

Core Features & Use Cases

  • Parallel CSV Wave Execution: Decompose source files into a tasks.csv and execute independent agents concurrently with configurable concurrency and resume support.
  • RED-GREEN TDD & Classification: Classify files into unit, integration, and e2e types, generate failing-first tests, and follow existing project test patterns to avoid stylistic drift.
  • Comprehensive Artifacts & Aggregation: Produce results.csv, discoveries.ndjson, context.md, and test-gen-report.json for verification, reporting, and downstream automation.
  • Use Case: Automatically generate tests for phase directories with gaps reported by verification.json or coverage-report.json, then run suite verification and summarize coverage deltas and discovered bugs.

Quick Start

Run the quality-test-gen command for the target phase to generate tests, aggregate results, and produce a test generation report.

Frequently Asked Questions about quality-test-gen

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

FAQPage Schema
How do I automatically generate unit, integration, and e2e tests for multiple source files at once?

Parallel test generation decomposes a codebase into a CSV of tasks and spawns concurrent agents to automatically produce unit, integration, and e2e tests. It classifies files, detects test frameworks, and generates failing-first tests following existing project patterns.

What is the best way to apply RED-GREEN TDD across a large codebase with coverage gaps?

RED-GREEN TDD at scale is applied by spawning parallel agents from a tasks.csv to generate failing-first tests across many source files simultaneously. This targets directories where verification.json or coverage-report.json indicate missing or partial coverage.

How does CSV wave execution work for concurrent test generation?

CSV wave execution works by decomposing source files into a tasks.csv and spawning independent agents concurrently with configurable concurrency limits. It supports resume functionality to automatically produce canonical artifacts like results.csv and discoveries.ndjson.

Can I generate tests automatically when verification.json shows partial coverage?

Yes, you can generate tests automatically when verification.json shows partial coverage. The process targets phase directories with coverage gaps, runs suite verification, and summarizes coverage deltas alongside any discovered bugs in a final test-gen-report.json.

What artifacts are produced by parallel CSV-driven test generation?

Parallel CSV-driven test generation produces canonical artifacts for verification and downstream automation, including results.csv, discoveries.ndjson, context.md, and test-gen-report.json. These files aggregate findings and report coverage deltas.

Do I need to manually configure test frameworks before generating tests with spawn agents?

No manual test framework configuration is needed before generating tests with spawn agents. The process automatically detects existing project test frameworks and follows current stylistic patterns to avoid stylistic drift when generating failing-first tests.