gsd-add-tests

Name: gsd-add-tests
Availability: InStock
Author: rkz91

Generate unit and E2E tests from phase specification files.

264|11|Updated Apr 25, 2026

Search Tags:#automation #test-generation #ci #unit-tests #e2e-tests #uat #phase-testing

Ready to run

npx skills add https://github.com/rkz91/coco --skill gsd-add-tests-rkz91

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-add-tests
Command: npx skills add https://github.com/rkz91/coco --skill gsd-add-tests-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate unit and end-to-end tests for a completed software phase based on UAT criteria and existing implementation.

Core Features & Use Cases

Test generation from phase specs (SUMMARY.md, CONTEXT.md, VERIFICATION.md). It classifies files into unit tests, E2E tests, or skips as non-testable. It supports generating tests for CI pipelines and local validation.
Use cases include validating completed phases, ensuring coverage, and scaffolding tests for continuous integration and regression testing.

Quick Start

Run the add-tests workflow for the current phase to generate unit and E2E tests from SUMMARY.md, CONTEXT.md, and VERIFICATION.md.

Frequently Asked Questions about gsd-add-tests

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

FAQPage Schema

How do I generate unit and E2E tests from phase specifications?▼

To generate unit and E2E tests from phase specifications, run the add-tests workflow using the SUMMARY.md, CONTEXT.md, and VERIFICATION.md files of a completed phase to classify files and scaffold tests with RED-GREEN verification.

What is the best way to automate test generation for CI pipelines?▼

Automating test generation for CI pipelines involves scaffolding tests from phase specifications and committing them with standardized messages like test(phase-{N}): add unit and E2E tests, ensuring local validation and regression testing coverage.

Do I need specific documentation files to generate tests for a completed phase?▼

Yes, generating tests for a completed phase requires SUMMARY.md, CONTEXT.md, and VERIFICATION.md files, which provide the implementation details and UAT criteria needed to classify files into unit tests, E2E tests, or non-testable skips.

How does RED-GREEN verification work when adding tests?▼

RED-GREEN verification works by implementing a deterministic workflow with a planning gate and test plan approval, ensuring generated tests initially fail (RED) before implementation is adjusted to make them pass (GREEN) for the completed phase.

Can I skip non-testable files when generating unit and E2E tests?▼

Yes, you can skip non-testable files during test generation because the workflow classifies each file from the phase context into unit tests, E2E tests, or skips them as non-testable based on the phase specifications.

How are generated tests committed to the repository?▼

Generated tests are committed to the repository using deterministic commit messages formatted as test(phase-{N}): add unit and E2E tests from add-tests command, ensuring clear tracking of automated test scaffolding for continuous integration.