skills.rest
acme-skunkworks
acme-skunkworksOFFICIAL
Explore all skills by this author →
GitHub

tdd

Guide Test-Driven Development with integration tests and the red-green-refactor loop.

Updated Apr 30, 2026
Search Tags:#tdd#test-driven development#software quality#red-green-refactor#test-first development
One-click install
npx skills add https://github.com/acme-skunkworks/eslint-config --skill tdd-acme-skunkworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/acme-skunkworks/eslint-config/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/acme-skunkworks/eslint-config --skill tdd-acme-skunkworks

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill guides users through the process of Test-Driven Development (TDD), helping to ensure that code quality is maintained and behavior is well-defined by tests.

Core Features & Use Cases

  • Test-Driven Development: Write tests before writing production code to ensure software quality.
  • Red-Green-Refactor Loop: Write a failing test, make it pass with minimal code, then refactor for better design.
  • Integration Tests: Focus on the interaction between components.
  • Use Case: When a developer wants to implement new features or fix bugs and wants to use TDD practices to ensure code reliability.

Quick Start

Start your TDD cycle by writing a test for the feature you want to implement, then write the code to make the test pass.

Frequently Asked Questions about tdd

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

FAQPage Schema
What is the red-green-refactor loop in test-driven development?▼

The red-green-refactor loop in test-driven development involves writing a failing test, implementing minimal code to pass it, then refactoring for better design. This cycle ensures software quality and behavior verification through tests.

How do I implement test-driven development for feature development and bug fixes?▼

To implement test-driven development for features and bug fixes, start by writing tests before production code. Follow the red-green-refactor loop, focusing on integration tests to verify component interactions and ensure code reliability.

When should I use test-first development in my software engineering workflow?▼

Use test-first development when implementing new features or fixing bugs to ensure code reliability. It maintains software quality by defining expected behavior through tests before writing the actual production code.

Does test-driven development focus on integration tests or unit tests?▼

Test-driven development as guided here focuses on integration tests, emphasizing the interaction between components. This approach ensures code quality and behavior verification during feature development and bug fixes.

Why write tests before implementing production code?▼

Writing tests before implementing production code ensures software quality and well-defined behavior. This test-driven development approach clarifies requirements upfront and verifies code reliability through the red-green-refactor loop.

Related Skills

Explore More Software Engineering Skills→
OutlineDrivenOutlineDriven
5

test-driven

Define and apply test-driven development practices across programming languages.

Official
Intermediate
CyapstayeCyapstaye
9

test-driven-development

Enforce the Red-Green-Refactor cycle with failing tests before implementation.

Community
Advanced
Patasse97Patasse97

tdd-guide

Generate tests, analyze coverage, and guide RED-GREEN-REFACTOR workflows across languages.

Community
Advanced
ArcadeAIArcadeAI
8

bdd

Structure Given/When/Then scenarios for behavior-driven development workflows.

Official
Intermediate