skills.rest
erikshafer
erikshaferCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tdd

Guide developers through the red-green-refactor loop for Test-Driven Development.

Updated Apr 21, 2026
Search Tags:#code quality#TDD#refactoring#test-driven development#software testing
One-click install
npx skills add https://github.com/erikshafer/CritterCab --skill tdd-erikshafer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/erikshafer/CritterCab/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/erikshafer/CritterCab --skill tdd-erikshafer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill aids in adopting Test-Driven Development (TDD) to improve code quality and reliability by guiding through the red-green-refactor loop.

Core Features & Use Cases

  • Red-Green-Refactor Loop: Walks through writing a failing test (RED), writing code to pass the test (GREEN), and refactoring for clarity (REFACTOR).
  • Integration Tests: Encourages writing integration-style tests that verify behavior through public interfaces.
  • Testable Design: Promotes interfaces that are easy to test and refactor without breaking tests.
  • Use Case: Ideal for developers looking to establish a test-first approach, or those who need to refactor legacy code with better test coverage.

Quick Start

Implement TDD by first writing a failing test for a new feature or bug fix, then write code to pass the test, and finally refactor the code to improve it.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I start test-driven development for a new feature?▼

Test-driven development begins by writing a failing test for the new feature, then writing code to pass the test, and finally refactoring for clarity. This red-green-refactor loop ensures code reliability and test coverage.

What is the red-green-refactor loop in software testing?▼

The red-green-refactor loop in software testing involves writing a failing test, writing code to make it pass, and refactoring to improve maintainability. This test-first approach verifies behavior through public interfaces.

How do I refactor legacy code with better test coverage?▼

Refactoring legacy code with better test coverage requires establishing a test-first approach by writing integration-style tests that verify behavior through public interfaces. This promotes testable design without breaking existing tests.

Does test-driven development work for integration tests?▼

Test-driven development works for integration tests by encouraging tests that verify behavior through public interfaces. This ensures the design remains easy to test and refactor without breaking tests during maintenance.

When do I need a test-first approach in software development?▼

A test-first approach is needed in software development when improving code quality and reliability for new features or bug fixes. It is ideal for developers establishing test coverage or refactoring legacy code.

Related Skills

Explore More Software Engineering Skills→
open-gsdopen-gsd
1.0k

tdd

Execute red-green-refactor cycles per vertical slice with public-interface tests.

Official
Advanced
martin-jancimartin-janci
3

test-driven-development

Write failing tests first to drive implementation and verify expected behavior.

Community
Advanced
TairitsuaTairitsua
13

code-simplifier

Simplify and refactor recently modified .NET C# code while preserving behavior.

Community
Intermediate
mikemylmikemyl
1

testing

Implement behavior-driven testing patterns through public APIs.

Community
Intermediate