gsd-add-tests

Generate unit and E2E tests from UAT criteria and implementation files.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-add-tests-dobrinz123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-add-tests
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-add-tests-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many completed development phases lack comprehensive automated tests and clear test plans tied to their UAT criteria and implementation details. This Skill analyzes phase artifacts and source code to produce a vetted test plan and concrete test files, removing manual guesswork and ensuring coverage aligns with verification criteria.

Core Features & Use Cases

  • Test plan generation: Inspect SUMMARY.md, CONTEXT.md, and VERIFICATION.md to derive UAT-driven test requirements and propose a prioritized plan for unit and E2E coverage.
  • File classification and RED-GREEN flow: Classify implementation files as TDD (unit), E2E (browser), or Skip, obtain user approval for the plan, and drive RED-GREEN test creation and verification.
  • Committing and gap reporting: Generate and commit test files with the required commit message, verify tests pass or report coverage gaps and next steps for engineers and QA.
  • Use Case: A developer finishing Phase 3 can quickly produce unit and E2E tests that reflect the documented verification criteria and integrate them into the repository.

Quick Start

Generate unit and E2E tests for phase 2 using its SUMMARY.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 UAT criteria automatically?

To generate unit and E2E tests from UAT criteria, the Skill inspects phase artifacts like SUMMARY.md, CONTEXT.md, and VERIFICATION.md to derive test requirements and proposes a prioritized coverage plan for approval.

How does the RED-GREEN test creation flow work for completed development phases?

The RED-GREEN test creation flow classifies implementation files as TDD, E2E, or Skip, then drives test creation and verification to ensure tests pass before committing them with a standardized message.

What source files do I need to generate a test plan for a development phase?

Generating a test plan requires SUMMARY.md, CONTEXT.md, and VERIFICATION.md files in the phase directory to map verification criteria to concrete unit and end-to-end test requirements.

Can I automatically commit generated test files using git during the TDD workflow?

Yes, you can automatically commit generated test files using git, as the Skill produces user-approved test files and commits them with the message test(phase-{N}): add unit and E2E tests from add-tests command.

What happens to uncovered code gaps after generating E2E and unit tests?

After generating E2E and unit tests, the Skill verifies whether tests pass and explicitly reports uncovered coverage gaps along with recommended next steps for engineers and QA.