spawn-test-case

Spawn test-case-agent after a successful commit to generate test cases.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/Zeliper/z-coder --skill spawn-test-case
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spawn-test-case
Source: https://github.com/Zeliper/z-coder/tree/main/.claude/skills/spawn-test-case
Command: npx skills add https://github.com/Zeliper/z-coder --skill spawn-test-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill delegates the generation of test cases to test-case-agent after a commit is completed, eliminating manual test design and ensuring coverage aligned with changes.

Core Features & Use Cases

  • Post-Commit Test Generation: Spawn test-case-agent only after commit-agent completes successfully.
  • Structured Test Files: Create tests under the ./Test/ directory following the TASK-ID naming conventions.
  • Localized Content & Coverage: Produce Korean test descriptions with English file names as required.

Quick Start

After a successful commit (e.g., TASK-001), spawn test-case-agent for Step 2, providing changed files and aStep description. The agent will generate corresponding test cases and place them under ./Test/.

Frequently Asked Questions about spawn-test-case

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

FAQPage Schema
How do I automate test-case generation after committing code changes?

Test-case generation automates the creation of test cases immediately after a successful commit. spawn-test-case delegates this work to test-case-agent, which generates structured tests aligned with your changes and places them in the ./Test/ directory following TASK-ID naming conventions.

Can I generate test cases for specific files or features I've implemented?

Yes. After a successful commit or by running /create-testcase, spawn-test-case spawns test-case-agent with your changed files and step description. The agent generates corresponding test cases for both task-based workflows and standalone file-based scenarios.

What agents and prerequisites do I need before spawning test-case generation?

Test-case generation requires coder-agent, builder-agent, and commit-agent to complete successfully first. spawn-test-case uses the Task tool to trigger test-case-agent only after these dependencies finish, ensuring tests are generated for validated, committed changes.

Where are generated test cases stored and how are they named?

Generated test cases are stored in the ./Test/ directory and follow TASK-ID naming conventions. Test descriptions are produced in Korean with English file names as required by your workflow standards.

Does test-case generation work in CI pipelines and commit workflows?

Yes. spawn-test-case is designed for commit workflows and CI pipelines. It automatically spawns test-case-agent only after commit-agent completes successfully, ensuring test generation is integrated into your continuous integration process.

What output does spawn-test-case provide after test cases are generated?

spawn-test-case outputs a concise result summary suitable for user reporting. This summary communicates the test generation status and results without verbose logging, making it easy to track test creation in commit workflows.