skills.rest
jmduea
jmdueaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-driven-development

Write failing tests before code using the red-green-refactor cycle.

Updated Feb 12, 2026
Search Tags:#testing#tdd#red-green-refactor#software-quality#test-driven-development#bug-prevention
One-click install
npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill test-driven-development-jmduea
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/jmduea/emotiv-cortex-rs/tree/main/.github/skills/test-driven-development
Command: npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill test-driven-development-jmduea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps developers prevent bugs and design flaws by enforcing a test‑first workflow, ensuring code meets intended behavior before it exists.

Core Features & Use Cases

  • Red‑Green‑Refactor Cycle: Write a failing test, make it pass with minimal code, then refactor safely.
  • Built‑in Guidance: Provides detailed steps, anti‑patterns, and verification checklists.
  • Applicable Scenarios: New feature development, bug fixes, refactoring, and behavior changes across any programming language.

Quick Start

Ask the AI to guide you through writing a failing test before implementing a new function.

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

Test-driven development enforces a test-first workflow to prevent bugs and design flaws by ensuring code meets intended behavior before it exists. It applies to feature development, bug fixing, and refactoring across software projects.

How do I start writing tests before code for a new feature?▼

To start writing tests before code, ask the AI to guide you through writing a failing test before implementing a new function. Follow the red-green-refactor cycle and use verification checklists to ensure tests fail first and pass after minimal implementation.

Can I use test-driven development for bug fixes and refactoring across any programming language?▼

Yes, you can use test-driven development for bug fixes, refactoring, and behavior changes across any programming language. The workflow applies universally to ensure code meets intended behavior through the red-green-refactor cycle.

What is the best way to prevent bugs early in software development?▼

Test-driven development prevents bugs early by enforcing a test-first workflow that catches design flaws before code exists. Writing tests first ensures implementation meets intended behavior through the red-green-refactor cycle.

Does test-driven development provide guidance on avoiding anti-patterns?▼

Yes, test-driven development provides built-in guidance including detailed steps, anti-patterns, and verification checklists. These ensure tests fail first and pass only after minimal implementation during the red-green-refactor cycle.

When should I not use a test-first workflow for software development?▼

Test-driven development is applicable for new feature development, bug fixes, refactoring, and behavior changes. If your task does not involve writing new code or modifying existing behavior, a test-first workflow may not be necessary.

Related Skills

Explore More Software Engineering Skills→
J-PsterJ-Pster
291

test-driven-development

Guide red-green-refactor cycles for opt-in test-driven development.

Community
Basic
testdoubletestdouble
198

refactor

Refactor code iteratively with test-gated validation after each step.

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

test-runner

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

Community
Intermediate
LambdaTestLambdaTest
350

lettuce-skill

Generate Lettuce BDD feature files and Python step definitions for web applications.

Official
Intermediate