gsd-add-tests

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams transform a completed phase's specifications into concrete test artifacts by analyzing phase documentation and implementation details.

Core Features & Use Cases

  • Classifies implementation files into TDD (unit), E2E (browser), or Skip categories and suggests targeted tests.
  • Presents a test plan for user approval before execution, ensuring alignment with UAT criteria.
  • Generates tests following RED-GREEN conventions and commits them with a standardized message.

Quick Start

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

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 completed project phases?

To generate unit and E2E tests from completed phases, this skill analyzes phase documentation like SUMMARY.md and CONTEXT.md to identify testing gaps and produce targeted test artifacts.

How does TDD test classification work for implementation files?

TDD test classification sorts implementation files into unit testing, E2E browser testing, or skip categories based on phase details, ensuring appropriate test coverage for each specific file type.

Can I review the test plan before the unit and E2E tests are generated?

Yes, you can review the test plan before generation. The skill presents a proposed test plan to ensure alignment with UAT criteria and waits for your explicit approval before creating any files.

What's the best way to automate test generation following RED-GREEN conventions?

Automating test generation with RED-GREEN conventions is handled by analyzing VERIFICATION.md to create tests, automatically committing them using a standardized message format for each phase.

Do I need specific phase documentation to identify testing gaps and generate tests?

Yes, you need completed phase documentation. The skill specifically requires SUMMARY.md, CONTEXT.md, and VERIFICATION.md files to analyze implementation details and identify existing testing gaps.

When should I skip automated test generation for a completed implementation phase?

You should skip automated test generation when implementation files lack clear unit or E2E browser testing targets, as the skill classifies unsuitable files into a skip category to prevent unnecessary tests.