Tdd

This skill should be used when the user asks to 'do TDD', 'test-driven development', 'red green refactor', 'write a failing test first', or wants to implement a feature using test-driven development.From its SKILL.md

Install

npx -y skills add 45ck/prompt-language --skill tdd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, as published. Nobody here has run it

Test-Driven Development

Implement the requested feature using strict TDD: red, green, refactor.

Use this when adding or changing behavior. Do not use this to recover an already failing test suite (use fix-and-test) or to perform behavior-preserving cleanup only (use refactor).

What to do

Read the feature requirement from the argument.
Add or update one test that expresses the next behavior slice.
Run the targeted test and confirm it fails first (red).
Implement the smallest change to pass that test (green).
Refactor with all tests still green before starting the next slice.

Flow

flow:
  retry max 5
    run: npm test
    if command_failed
      prompt: Read the test failures. If no test exists yet for the feature, write one (red phase). Otherwise fix the implementation to make it pass (green phase). Only write minimum code needed.
    end
  end

done when:
  tests_pass
  lint_pass

Rules

Always create the failing test before implementation for new behavior.
The test must fail before you write implementation code. If it passes immediately, the test is not testing the new behavior.
Write the minimum code to pass. Do not over-engineer.
Once green, refactor for clarity. Do not add new behavior during refactor.

Examples

For language-specific TDD loop command examples, see examples/multi-ecosystem.md.