gsd-testing

Generate unit, integration, and end-to-end tests while managing related todos.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/da-moon/manus-skills --skill gsd-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-testing
Source: https://github.com/da-moon/manus-skills/tree/main/skills/gsd-testing
Command: npx skills add https://github.com/da-moon/manus-skills --skill gsd-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It eliminates the manual, error-prone process of writing tests and tracking test-related work by automatically generating appropriate tests and organizing todos for delivery teams.

Core Features & Use Cases

  • Generate unit, integration, and end-to-end tests from code and requirements to ensure coverage.
  • Create and manage todos for test-related work to keep teams aligned.
  • Adapt test generation workflows across languages and frameworks, updating tests as code evolves with changes in requirements.

Quick Start

Tell it to generate tests for a module and organize the related todos.

Frequently Asked Questions about gsd-testing

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

FAQPage Schema
How do I automatically generate unit and integration tests from existing code?

To automatically generate unit and integration tests, this Skill identifies target code from your requirements and phase work, then produces corresponding test suites. It adapts to codebases across languages to ensure coverage.

Can I track test-related todo items alongside automated test generation?

Yes, you can track test-related todo items alongside automated test generation. This Skill creates and manages todos for discovered test work, keeping delivery teams aligned and organized throughout the workflow.

Does automated test generation work across different programming languages?

Automated test generation works across different programming languages by identifying targets from requirements. It adapts workflows for various frameworks and updates tests as your code evolves with changing requirements.

What is the best way to manage end-to-end test creation and related todos?

The best way to manage end-to-end test creation and todos is to use a Skill that generates tests from code while simultaneously tracking related work. This eliminates manual errors and organizes delivery tasks.

Do I need a references folder to support test generation and discovery?

You do not strictly need a references folder, but it is supported for defining conventions. The Skill uses this folder, along with optional scripts and assets, to satisfy workflow requirements for discovery via frontmatter.

How do I generate tests for a specific module and organize the related todos?

To generate tests for a specific module and organize related todos, simply instruct the Skill to target that module. It will produce unit, integration, and end-to-end tests while tracking associated delivery items.