skills.rest
JeremyDev87
JeremyDev87COMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-driven-development

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

31|3|Updated Dec 12, 2025
Search Tags:#workflow#testing#tdd#code-quality#software-engineering#test-driven-development
One-click install
npx skills add https://github.com/JeremyDev87/codingbuddy --skill test-driven-development-jeremydev87
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/JeremyDev87/codingbuddy/tree/main/packages/rules/.ai-rules/skills/test-driven-development
Command: npx skills add https://github.com/JeremyDev87/codingbuddy --skill test-driven-development-jeremydev87

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This section describes how teams can prevent regressions by forcing the creation of failing tests before implementation, ensuring code behavior is validated early.

Core Features & Use Cases

  • Red-Green-Refactor cycle to drive code quality.
  • Clear test naming and scope to document expected behavior.
  • Safe guidance for feature work, bug fixes, and refactors with incremental development.

Quick Start

Enforce a failing test, implement the minimal code to pass it, and refactor.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I prevent code regressions when adding new features?▼

Prevent code regressions by enforcing test-first development, which validates behavior early. You write an explicit failing test before implementation, ensuring new features do not break existing software project functionality.

What is the Red-Green-Refactor cycle in test-driven development?▼

The Red-Green-Refactor cycle drives code quality by first writing a failing test, then implementing minimal production code to pass it, and finally refactoring safely. This disciplined workflow protects against regressions across software projects.

How to start writing tests first for a bug fix?▼

Start a bug fix by writing a clear, failing test that documents the expected behavior. Apply minimal production code to pass the test, ensuring the specific bug is resolved and protected against future regressions.

Does test-driven development work for refactoring existing code?▼

Yes, test-driven development works for refactoring by providing safe guidance through incremental development. Clear test scope and validated behavior ensure you can refactor production code without introducing regressions.

What is the best way to document expected code behavior during testing?▼

The best way to document expected behavior is by applying clear test naming and scope within your test-first workflow. These failing tests serve as explicit, validated documentation for your software project's required functionality.

Related Skills

Explore More Software Engineering Skills→
DocaariDocaari
1

test-writer

Generate executable tests from project specs and architecture diagrams.

Community
Advanced
MomoDavilukeMomoDaviluke
2

test-driven-development

Implement a red-green-refactor test-driven development workflow with failing tests first.

Community
Intermediate
Matt-Aurora-VenturesMatt-Aurora-Ventures
58

test-driven-development

Automate red-green-refactor cycles with failing-test-first workflows.

Community
Intermediate
udsy19udsy19

incremental-implementation

Breaks down big-bucket projects into manageable pieces with step-by-step implementation and verification.

Community
Intermediate