test-driven-development

Enforce TDD Red-Green-Refactor cycles for Godot/GDScript with GUT.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/OpenSourceSam/v2_heras_garden --skill test-driven-development-opensourcesam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/OpenSourceSam/v2_heras_garden/tree/main/.claude/skills/test-driven-development
Command: npx skills add https://github.com/OpenSourceSam/v2_heras_garden --skill test-driven-development-opensourcesam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a rigorous Test-Driven Development (TDD) methodology to ensure code quality, prevent regressions, and build robust software by requiring tests to be written before implementation code.

Core Features & Use Cases

  • TDD Enforcement: Mandates writing failing tests before any production code.
  • Red-Green-Refactor Cycle: Guides users through the core TDD loop.
  • Godot/GDScript Integration: Provides specific guidance for TDD within the Godot engine using the GUT framework.
  • Use Case: When developing a new feature for the game, use this Skill to write a test that defines the expected behavior, then write the minimal code to make that test pass, ensuring the feature works as intended from the start.

Quick Start

Use the test-driven-development skill to write a failing test for the new player movement logic.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I enforce test-driven development principles when writing GDScript in Godot?

Test-driven development in Godot is enforced by mandating failing tests before implementation, specifically guiding you through the Red-Green-Refactor cycle using the GUT framework to ensure code quality and prevent regressions.

What is the Red-Green-Refactor cycle for test-driven development?

The Red-Green-Refactor cycle is a core TDD loop where you write a failing test first, implement the minimal production code to make it pass, and then refactor the code to ensure robust software and prevent regressions.

How do I start writing a failing test for new game features?

To start writing a failing test for new game features, define the expected behavior in a test first, then write the minimal code required to make that test pass, ensuring the feature works as intended from the start.

Does TDD guidance include specific protocols for bug fixes and refactoring?

TDD guidance includes strict testing protocols for all new features, bug fixes, and refactoring, requiring adherence to the Red-Green-Refactor cycle to verify code quality and prevent future regressions.