skills.rest
Jhabbig
JhabbigCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Write a failing test before implementing code to enforce red-green-refactor discipline.

Updated Apr 5, 2026
Search Tags:#unit tests#testing#tdd#refactoring#regression prevention#red-green-refactor#bug fixes
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill test-driven-development-jhabbig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/skills/test-driven-development
Command: npx skills add https://github.com/Jhabbig/Habbig --skill test-driven-development-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents you from writing production code before you have a failing test that proves the behavior you want, reducing guesswork and regressions.

Core Features & Use Cases

  • Test-First Workflow: Write the test before implementation so the failure confirms the test is meaningful.
  • Red-Green-Refactor Discipline: Move from failing test to minimal passing code, then clean up without changing behavior.
  • Regression Protection: Use it for new features, bug fixes, and refactors where you need reliable proof that changes do what they should.
  • Use Case: When fixing a bug or adding a feature, this Skill helps you define the expected behavior, verify the failure, implement the smallest fix, and keep the suite green.

Quick Start

Use the test-driven-development skill to write a failing test for the behavior you want, then implement only enough code to make it pass.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I start test-driven development when fixing a bug?▼

Test-driven development for a bug fix starts by writing a failing test that reproduces the specific bug. You verify the test fails for the right reason, implement the minimal code fix to make it pass, and then refactor without changing behavior.

What is the red-green-refactor cycle in unit testing?▼

The red-green-refactor cycle is a unit testing discipline where you first write a failing test (red), implement the minimal code to make it pass (green), and then clean up the code without changing behavior (refactor).

When should I use a test-first workflow for refactoring code?▼

You should use a test-first workflow for refactoring when you need reliable regression protection. It ensures you define expected behavior with a failing test before changing code, proving your refactoring does not break existing functionality.

Does test-driven development require verifying why a unit test fails?▼

Yes, test-driven development requires verifying that the unit test fails for the right reason before writing code. This confirms the test is meaningful and actually targets the intended behavior.

What is the best way to prevent regressions when adding new features?▼

The best way to prevent regressions when adding new features is using a test-first workflow. Writing a failing test that proves the desired behavior before implementation reduces guesswork and ensures reliable code.

Related Skills

Explore More Software Engineering Skills→
caobingshengcaobingsheng
1

tdd-workflows-tdd-red

Generate failing tests to define expected behavior in the TDD red phase.

Community
Advanced
dmedina-devdmedina-dev
1

test-driven-development

Write failing tests before implementing code in JavaScript or TypeScript projects.

Community
Basic
WhatIfWeDigDeeperWhatIfWeDigDeeper
1

refactor

Refactor code by extracting functions, renaming variables, and simplifying logic.

Community
Intermediate
FerroxLabsFerroxLabs
21

ferrox-test-driven-development

Enforce test-first development with failing tests before production code.

Community
Advanced