skills.rest
liamtran96
liamtran96COMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce a red-green-refactor cycle by writing failing tests before production code.

Updated Jan 30, 2026
Search Tags:#code quality#unit tests#workflow#software engineering#TDD#test-driven development#red green refactor
One-click install
npx skills add https://github.com/liamtran96/msm-car-booking --skill test-driven-development-liamtran96
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/liamtran96/msm-car-booking/tree/main/.claude/skills/test-driven-development
Command: npx skills add https://github.com/liamtran96/msm-car-booking --skill test-driven-development-liamtran96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill formalizes a test-first workflow that ensures developers begin by writing a failing test, preventing unverified changes and catching regressions early.

Core Features & Use Cases

  • Test-first workflow: guides writing a failing test before any production code.
  • Minimal implementation: encourages keeping production code small and focused until tests pass.
  • Red-Green-Refactor discipline: promotes iterative design until all tests pass.
  • Applicable scenarios: new features, bug fixes, refactors, and behavioral changes across modules.

Quick Start

Start by writing a failing test for the target behavior, run the tests to observe the failure, implement the smallest code necessary to make the test pass, re-run tests until green, and then refactor for clarity and maintainability.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
What is test-driven development and how does the red-green-refactor cycle work?▼

Test-driven development (TDD) is a workflow where you write a failing test before production code. The red-green-refactor cycle means observing a test failure, writing minimal code to pass it, then refactoring for clarity and maintainability.

How do I apply test-driven development to bug fixes and refactoring?▼

To apply test-driven development to bug fixes and refactors, first write a failing test that captures the target behavioral change or bug. Implement the smallest code necessary to make the test pass, ensuring verifiable and reliable behavior.

When should I use a test-first workflow for writing unit tests?▼

Use a test-first workflow when implementing new features, fixing bugs, or refactoring across modules. It prevents unverified changes by requiring minimal, verifiable tests upfront, ensuring you catch regressions early before production code is written.

What is the best way to ensure code quality through minimal implementation in TDD?▼

The best way to ensure code quality in TDD is keeping production code small and focused until tests pass. Write the smallest code necessary to satisfy the failing test, then refactor for clarity to maintain reliable behavior and discipline.

Does test-driven development require specific testing frameworks to implement?▼

No, test-driven development does not require specific testing frameworks. It is a workflow discipline applicable across projects and modules, relying on the red-green-refactor cycle rather than specific dependencies or component tools.

Related Skills

Explore More Software Engineering Skills→
rbaumierrbaumier
4

tdd

Enforce failing tests before production code using Red-Green-Refactor cycles.

Community
Intermediate
axiomanticaxiomantic
8

test-driven-development

Enforce a red-green-refactor workflow by writing failing tests before production code.

Official
Intermediate
obraobra
41

Test-Driven Development (TDD)

Enforce test-first development using the red-green-refactor cycle.

Community
Basic
AsiaOstrichAsiaOstrich
70

ATDD 助手

Guide teams through ATDD workflows with Given-When-Then acceptance criteria.

Community
Intermediate