skills.rest
synqing
synqingCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce test-driven development by requiring a failing test before implementation.

1|Updated Dec 23, 2025
Search Tags:#testing#tdd#qa#quality#red-green-refactor
One-click install
npx skills add https://github.com/synqing/Lightwave-Ledstrip --skill test-driven-development-synqing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/synqing/Lightwave-Ledstrip/tree/main/.claude/skills/test-driven-development
Command: npx skills add https://github.com/synqing/Lightwave-Ledstrip --skill test-driven-development-synqing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces Test-Driven Development by guiding you to write tests before implementation.

Core Features & Use Cases

  • Red-Green-Refactor: The cycle of testing and refactoring
  • Mandatory failing test: Ensure test drives design
  • Clear guidance: Steps and examples for popular languages

Quick Start

Use TDD: write a failing test for a new function, then implement

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I write tests before implementing code?▼

Test-driven development starts by writing a failing test that specifies the desired behavior, then writing the minimum code to pass it. This Red-Green-Refactor cycle ensures tests drive your design and implementation from the start.

What is the Red-Green-Refactor workflow?▼

Red-Green-Refactor is a three-step cycle: write a failing test (Red), implement code to pass it (Green), then improve the code without changing behavior (Refactor). This enforces test coverage and clean code iteratively.

Can I apply test-driven development to existing codebases?▼

Yes, TDD applies to feature work, bug fixes, refactoring, and behavior changes across both new and existing codebases. Start by writing a failing test for any change, then implement against it.

Why require a failing test before writing production code?▼

A failing test ensures the test actually validates new behavior rather than passing by accident. It confirms your test suite catches regressions and drives implementation decisions aligned with requirements.

Does test-driven development work for all project types?▼

TDD is effective for feature development, bug fixes, and refactoring across codebases of any size. The Red-Green-Refactor pattern applies regardless of language or framework, though syntax and tools vary.

Related Skills

Explore More Software Engineering Skills→
GGPromptsGGPrompts
147

running-tests

Discover and run Jest, Pytest, Cargo, and Go tests with a 300-second timeout.

Community
Intermediate
mayurpisemayurpise
39

coverage

Aggregate coverage reports across languages to identify untested code paths.

Community
Intermediate
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic
mazreanmazrean

creating-test-cases

Design test cases using boundary value analysis and equivalence partitioning.

Community
Advanced