gsd-add-tests

Generate unit and E2E tests from phase documentation and commit them.

Updated Apr 2, 2026

Search Tags:#automation #unit-testing #e2e-testing #generate #tests #test-planning

Ready to run

npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill gsd-add-tests-ev3rlit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-add-tests
Source: https://github.com/ev3rlit/magam-canonical-archive/tree/main/.codex/skills/gsd-add-tests
Command: npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill gsd-add-tests-ev3rlit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate tests from phase documentation to verify implementation against UAT criteria.

Core Features & Use Cases

Analyze SUMMARY.md, CONTEXT.md, and VERIFICATION.md to categorize tests into unit, E2E, or skip.
Generate a validated test plan with acceptance criteria and gating steps for stakeholder approval.
Produce test scaffolds and commit changes with a standardized message: test(phase-N): add unit and E2E tests from add-tests command.

Quick Start

Run the add-tests workflow on the completed phase to generate and commit unit and E2E tests.

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 documentation?▼

You can generate unit and E2E tests by running the add-tests workflow on completed phases, which analyzes SUMMARY.md, CONTEXT.md, and VERIFICATION.md to categorize and scaffold tests automatically.

Can I automatically commit test files with a standardized message?▼

Yes, automated test generation includes committing test scaffolds with a standardized message format: test(phase-N): add unit and E2E tests from add-tests command.

How does test classification decide between unit, E2E, and skip categories?▼

Test classification analyzes phase artifacts like SUMMARY.md and VERIFICATION.md to evaluate acceptance criteria, then categorizes each test into unit, E2E, or skip based on the documented requirements.

What phase artifacts are required to generate a test plan for approval?▼

Generating a test plan requires completed phase artifacts including SUMMARY.md, CONTEXT.md, and VERIFICATION.md to validate acceptance criteria and gating steps for stakeholder approval.

Does the test generation workflow support the RED-GREEN testing process?▼

Yes, the test generation workflow explicitly satisfies the RED-GREEN workflow by producing test scaffolds from phase documentation that verify implementation against UAT criteria before execution.

When should I skip test generation for completed phase artifacts?▼

You should skip test generation when phase artifacts lack sufficient verification context, since the workflow requires SUMMARY.md, CONTEXT.md, and VERIFICATION.md to classify and scaffold tests accurately.