gen-tests

Generate unit, integration, and end-to-end tests for web apps and APIs.

6|2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/i-standard1/yamasaki --skill gen-tests-i-standard1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-tests
Source: https://github.com/i-standard1/yamasaki/tree/main/.claude/skills/gen-tests
Command: npx skills add https://github.com/i-standard1/yamasaki --skill gen-tests-i-standard1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and enhancement of tests to support a TDD-first workflow.

Core Features & Use Cases

  • Generate unit, integration, and end-to-end tests based on design docs and requirements.
  • Extend existing test suites by adding new test cases and refactoring failing specs.
  • Support templates for different test types, with stubs/mocks to keep builds GREEN during development.

Quick Start

Run the test generation command to create and augment tests for your project.

Frequently Asked Questions about gen-tests

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

FAQPage Schema
How do I generate unit and e2e tests for a TDD workflow?

You can generate unit and e2e tests by running the test generation command to create and augment tests based on design docs. It uses templates and mappings to produce test code, supporting a TDD-first workflow across web apps and APIs.

Can I extend existing test suites without breaking my current build?

Yes, you can extend existing test suites by adding new test cases and refactoring failing specs. The tool supports mocking external dependencies and marks non-implemented hooks with stubs to keep your builds green during development.

Does this test generation tool work with Jest and Playwright?

Yes, the tool works across unit, integration, and end-to-end tests for modern web apps and APIs. It supports TDD-first workflows using frameworks like Jest and Playwright to generate and enhance test cases.

What is the best way to automate test creation from design requirements?

Automating test creation from design requirements involves using templates and mappings to produce test code. This approach generates new test cases, extends existing suites, and replaces failing specs while keeping builds green with stubs and mocks.

How do I replace failing specs during test-driven development?

You can replace failing specs during test-driven development by running the test enhancement command. It refactors failing tests and uses stubs for non-implemented hooks to maintain green builds while you develop the underlying functionality.