practicing-tdd

Enforce a RED-GREEN-REFACTOR cycle with failing tests before code changes.

5|1|Updated Sep 6, 2009
One-click install
npx skills add https://github.com/bnadlerjr/dotfiles --skill practicing-tdd-bnadlerjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: practicing-tdd
Source: https://github.com/bnadlerjr/dotfiles/tree/main/claude/skills/practicing-tdd
Command: npx skills add https://github.com/bnadlerjr/dotfiles --skill practicing-tdd-bnadlerjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure that code changes are driven by failing tests, preventing silent regressions and guiding design.

Core Features & Use Cases

  • Enforces a strict RED-GREEN-REFACTOR cycle to keep tests at the center of development.
  • Provides clear guidance for when to use TDD during feature work, bug fixes, and refactoring.
  • Supports consistent test creation, maintenance, and safe refactoring practices across projects.

Quick Start

Write a failing test that describes the desired behavior, then implement the minimal code to pass and refactor.

Frequently Asked Questions about practicing-tdd

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

FAQPage Schema
How does test-driven development prevent silent regressions?

Test-driven development prevents silent regressions by enforcing a test-first workflow where code changes are driven by failing tests, ensuring every new implementation is guarded by automated verification.

What is the RED-GREEN-REFACTOR cycle in software testing?

The RED-GREEN-REFACTOR cycle in software testing dictates writing a failing test, implementing minimal code to pass it, then refactoring safely. This strict sequence keeps tests central to development and guides design.

How do I apply TDD during bug fixes and refactoring?

To apply TDD during bug fixes and refactoring, you first write a failing test capturing the bug or desired behavior, implement the minimal code to pass it, and then refactor safely while maintaining strong regression guards.

When should I use test-driven development for feature work?

You should use test-driven development for feature work when your team wants strong regression guards and consistent test maintenance. It codifies a strict cycle to ensure feature changes are always driven by failing tests.

What is the best way to maintain discipline around test creation?

The best way to maintain discipline around test creation is to enforce a strict RED-GREEN-REFACTOR cycle, promoting minimal implementations and ensuring tests are written before code changes are made.