tdd

Enforce red-green-refactor cycles by writing failing tests before implementation.

153|12|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/jmstar85/oh-my-githubcopilot --skill tdd-jmstar85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/jmstar85/oh-my-githubcopilot/tree/main/.github/skills/tdd
Command: npx skills add https://github.com/jmstar85/oh-my-githubcopilot --skill tdd-jmstar85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Red-Green-Refactor workflow and test-centric discipline are hard to sustain without clear guidance. This skill codifies a repeatable TDD process to ensure tests drive design and prevent feature creep.

Core Features & Use Cases

  • Enforces Red-Green-Refactor cycle per feature.
  • Promotes naming tests as specifications and incremental design.
  • Provides a repeatable protocol for test-first development and safe refactoring across languages and frameworks.

Quick Start

Run the Red-Green-Refactor cycle for the next feature by writing a failing test first, then implementing only enough code to pass.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I enforce a red-green-refactor cycle for unit tests?

You can enforce a red-green-refactor cycle by writing a failing unit test first, implementing only enough code to pass, and then refactoring safely. This test-first workflow drives design and prevents feature creep across languages and frameworks.

What is test-driven development and how does it prevent feature creep?

Test-driven development is a test-first workflow where tests drive software design and prevent feature creep. It codifies a repeatable process of writing failing tests before implementation to ensure consistent, reliable code.

Does test-driven development work with any programming language or testing framework?

Yes, test-driven development is framework-agnostic and applies to software projects employing unit tests across languages and frameworks. It provides repeatable guidance for test-first development regardless of your specific tech stack.

How do I name unit tests as specifications in a TDD workflow?

You name unit tests as specifications by treating test names as descriptive requirements within your test-first workflow. This practice promotes incremental design and ensures your tests clearly document expected behavior across frameworks.

What is the best way to start a test-first development workflow?

The best way to start a test-first development workflow is to run the red-green-refactor cycle for your next feature by writing a failing test first, then implementing only enough code to make it pass.