tdd-green

Implement minimal code to turn failing unit tests green.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nikoheikkila/agents --skill tdd-green-nikoheikkila
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-green
Source: https://github.com/nikoheikkila/agents/tree/main/skills/tdd-green
Command: npx skills add https://github.com/nikoheikkila/agents --skill tdd-green-nikoheikkila

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement minimal code to make failing unit tests pass without over-engineering.

Core Features & Use Cases

  • Provides a disciplined approach to turning red tests green by adding only the smallest amount of code required.
  • Keeps tests unmodified, ensuring the red-green-refactor cycle remains clean and reliable.
  • Ideal for feature work where quick validation of behavior is needed without expanding scope.

Quick Start

Provide failing tests and instruct the AI to implement the smallest code necessary to turn the test suite green.

Frequently Asked Questions about tdd-green

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

FAQPage Schema
How do I implement minimal code to turn failing unit tests green without over-engineering?

To turn failing unit tests green, this Skill applies the Transformation Priority Premise to generate only the minimal code required, preventing unnecessary features and keeping your red-green-refactor cycle clean.

What is the best way to fix failing tests without modifying the test suite?

The best way to fix failing tests without modifying them is to enforce strict scoping that adds only the smallest amount of code necessary, ensuring your unit tests remain unmodified and reliable.

How does the Transformation Priority Premise help with refactoring code?

The Transformation Priority Premise guides refactoring by enforcing strict behavioral rules that prioritize the smallest possible code transformations, ensuring changes stay within the scope of the failing test.

Can I use this approach to fix failing tests that involve external dependencies?

You cannot use this approach to fix failing tests involving external dependencies, as it strictly avoids them along with test edits and unnecessary features to keep the unit test suite clean.

When do I need a minimal implementation approach for my unit tests?

You need a minimal implementation approach for unit tests when doing feature work where quick validation of behavior is required, ensuring you do not expand scope beyond the failing test.