skills.rest
Veraticus
VeraticusCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce RED-GREEN-REFACTOR cycles with failing tests before production code.

Updated Jan 23, 2026
Search Tags:#testing#tdd#refactoring#go#red-green-refactor#code-quality#test-driven-development
One-click install
npx skills add https://github.com/Veraticus/gambit --skill test-driven-development-veraticus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/Veraticus/gambit/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/Veraticus/gambit --skill test-driven-development-veraticus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces adherence to the RED-GREEN-REFACTOR cycle, ensuring that no production code is written without a failing test first, thereby increasing reliability and maintainability.

Core Features & Use Cases

  • Enforces a test-first workflow for feature development, bug fixes, and refactoring.
  • Guides teams through writing failing tests, implementing minimal code, and validating green results.
  • Provides a clear, auditable process that improves code quality and maintainability.

Quick Start

Create a failing test for a new behavior, run the test suite to observe failure, implement minimal code to pass, re-run tests to confirm all pass, and commit the green result.

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 a strict test-driven development workflow in Go?▼

To enforce test-driven development in Go, this skill mandates a RED-GREEN-REFACTOR cycle. It requires writing a failing test first, implementing minimal production code to pass it, running the full test suite, and verifying a green result before committing.

What is the RED-GREEN-REFACTOR cycle for code correctness?▼

The RED-GREEN-REFACTOR cycle is a test-driven development process that guarantees code correctness by requiring a failing test, writing minimal code to pass that test, and then refactoring while maintaining green test results.

How do I start writing failing tests before implementing production code?▼

To start writing failing tests before production code, create a failing test for a new behavior, run the test suite to observe failure, implement minimal code to pass, re-run tests to confirm all pass, and commit the green result.

Can I use this TDD workflow for bug fixes and refactoring?▼

Yes, you can use this TDD workflow for bug fixes and refactoring. It applies test-first development across feature development, bug fixes, and refactoring in Go projects to increase reliability and maintainability.

Why does test-driven development require a failing test first?▼

Test-driven development requires a failing test first to ensure no production code is written without a corresponding test. This increases reliability and maintainability by providing an auditable process that validates behavior before implementation.

Does this TDD skill work without external dependencies?▼

Yes, this TDD skill works without external dependencies. It requires no additional components or dependencies to enforce the test-first workflow and RED-GREEN-REFACTOR cycle across your Go projects.

Related Skills

Explore More Software Engineering Skills→
tneztnez

bootstrap

Initialize the .docent directory structure and configuration for new projects.

Community
Basic
HomericIntelligenceHomericIntelligence
18

run-tests

Execute Mojo or Python test suites and generate validation reports.

Official
Basic
thangvawnthangvawn

plankton-code-quality

Automate code quality enforcement with formatters, linters, and Claude subprocesses.

Community
Advanced
skeeper75skeeper75

moai-workflow-tdd

Guide developers through the RED-GREEN-REFACTOR TDD cycle for new features.

Community
Intermediate