skills.rest
ctrlShiftBryan
ctrlShiftBryanCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce test-driven development by writing failing tests before implementing code.

Updated Aug 27, 2026
Search Tags:#testing#tdd#refactoring#quality#software-engineering#tests-first
One-click install
npx skills add https://github.com/ctrlShiftBryan/dotfiles --skill test-driven-development-ctrlshiftbryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/ctrlShiftBryan/dotfiles/tree/main/claude/.claude/skills/test-driven-development
Command: npx skills add https://github.com/ctrlShiftBryan/dotfiles --skill test-driven-development-ctrlshiftbryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD helps teams write reliable code by forcing tests before implementation, preventing regressions and guiding design.

Core Features & Use Cases

  • Red-Green-Refactor cycle: Write a failing test, then implement the minimal code to pass and refactor.
  • Guided development discipline: Encourages thinking through requirements via tests before coding.
  • Applicability: Suitable for new features, bug fixes, and refactors across software projects to ensure correct behavior.

Quick Start

Write a failing test for the new behavior, then implement the minimal code to make the test pass, and refactor.

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?▼

Use test-driven development for new features, bug fixes, and refactoring to ensure correct behavior before coding. It forces you to think through requirements via tests, preventing regressions and guiding software design.

How do I start writing tests first when implementing a new software feature?▼

To start test-driven development, write a failing test that defines the desired new behavior, implement the absolute minimal code to make that test pass, and refactor the implementation while maintaining green tests.

Can I use test-first development for bug fixes and refactoring existing code?▼

Yes, test-first development is applicable to bug fixes and refactoring across software projects. You write a test capturing the correct behavior before changing code, ensuring regressions are caught immediately.

Does test-driven development require any specific testing frameworks or dependencies?▼

No specific testing frameworks or dependencies are required. Test-driven development is a discipline applicable across software projects, relying on the red-green-refactor workflow rather than particular tools.

What's the difference between test-driven development and writing tests after implementation?▼

Test-driven development forces you to write tests before implementation, guiding design and preventing regressions from the start. Writing tests after coding validates existing behavior but lacks the design discipline of tests-first development.

Related Skills

Explore More Software Engineering Skills→
timbuchingertimbuchinger
1

test-driven-development

Enforce writing failing tests before implementing minimal code to pass.

Community
Basic
InverterNetworkInverterNetwork

test-driven-development

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

Official
Advanced
d-o-hubd-o-hub
11

test-runner

Run Rust unit, integration, and doc tests with cargo test.

Community
Intermediate
iCesofTiCesofT
1

bdd-patterns

Apply Behavior-Driven Development patterns with Given-When-Then scenarios and feature files.

Community
Intermediate