test-suite-create

Create unit, integration, and end-to-end tests for a feature.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/cpa03/blueprintify --skill test-suite-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-suite-create
Source: https://github.com/cpa03/blueprintify/tree/main/.opencode/skill/test-suite-create
Command: npx skills add https://github.com/cpa03/blueprintify --skill test-suite-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of thorough test suites to validate new features, reducing manual test design time and improving coverage.

Core Features & Use Cases

  • Generates unit, integration, and end-to-end tests based on feature scope.
  • Suggests edge cases and happy paths, then scaffolds test files.
  • Use Case: A new feature is ready for release; this skill creates a ready-to-run test suite and supports CI integration.

Quick Start

Generate a complete test suite for a feature by identifying targets, outlining edge cases, and scaffolding test files.

Frequently Asked Questions about test-suite-create

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

FAQPage Schema
How do I automatically generate a test suite for a new feature?

To automatically generate a test suite, this skill identifies feature targets, outlines edge cases and happy paths, and scaffolds ready-to-run test files for unit, integration, and end-to-end coverage.

What is feature test scaffolding and how does it improve test coverage?

Feature test scaffolding automatically generates structured test files for unit and integration tests, reducing manual test design time and validating edge cases to ensure comprehensive test coverage for new features.

Can I use automated test generation for CI integration workflows?

Yes, automated test generation applies directly to feature development workflows by scaffolding ready-to-run test suites and defining requirements for test templates, naming conventions, and coverage validation for CI integration.

What's the best way to build unit and integration tests for feature development?

The best way to build unit and integration tests is to automate suite creation based on feature scope, which suggests edge cases, defines naming conventions, and scaffolds comprehensive test files.

Do I need to manually define test templates and naming conventions for end-to-end tests?

No, you do not need to manually define test templates and naming conventions for end-to-end tests, because the automated suite generation defines these requirements while scaffolding the test files.

Why does test suite creation focus on edge cases and happy paths?

Test suite creation focuses on edge cases and happy paths to validate feature scope thoroughly, ensuring the generated unit and integration tests provide robust coverage and catch potential regressions before release.