skill-create-test

Automate design-first test planning and plan-to-test generation for Go projects.

Updated Oct 27, 2025
One-click install
npx skills add https://github.com/mariotoffia/gobridge --skill skill-create-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-create-test
Source: https://github.com/mariotoffia/gobridge/tree/main/.cursor/skills/skill-create-test
Command: npx skills add https://github.com/mariotoffia/gobridge --skill skill-create-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the design-first test planning workflow for Go projects.

Core Features & Use Cases

  • Design-first test planning: Create a formal test plan before writing code, including unit/integration/simulation/e2e classifications and edge cases.
  • Automated plan-to-test generation: Generate test files and structures from the approved plan and maintain traceability.
  • Determinism and documentation: Enforce deterministic tests, track decisions, and update documentation after validation.

Quick Start

Provide input Go package and requirements, invoke the design-first workflow, confirm readiness, then generate tests and update the test index.

Frequently Asked Questions about skill-create-test

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

FAQPage Schema
How do I generate deterministic Go unit tests from a design plan?▼

Deterministic Go unit tests are generated by first creating a formal test plan, then automatically generating test files and structures from that plan while maintaining traceability. This enforces deterministic execution and tracks edge cases.

What is the design-first test planning workflow for Go integration testing?▼

Design-first test planning is a workflow that creates a formal test plan before writing code, classifying scenarios into unit, integration, simulation, and e2e categories to ensure comprehensive coverage and edge case handling.

How do I maintain test indices and documentation after validating Go tests?▼

Test indices and documentation are automatically updated after successful test validation by the agent workflow, ensuring traceability and tracking decisions made during the plan-to-test generation process.

Can I use this for both unit and end-to-end testing in Go codebases?▼

Yes, the workflow applies to unit, integration, simulation, and end-to-end testing scenarios across Go codebases, guiding plan-to-test generation and validation for all these classifications.

Do I need an explicit test plan before generating Go tests?▼

Yes, explicit plan creation is required before test generation. The workflow mandates agent collaboration using a test-designer and test-reviewer to validate the plan before generating any test files.

Why does my Go test generation require a test-designer and test-reviewer?▼

The test-designer and test-reviewer agents are required to enforce the design-first workflow, ensuring the formal test plan is validated for determinism and edge cases before automated test generation begins.