skills.rest
Tromml
TrommlOFFICIAL
Explore all skills by this author →
WebsiteGitHub

kimchi:tdd

Enforce the RED-GREEN-REFACTOR cycle for all code implementation and bug fixes.

8|Updated Jan 31, 2026
Search Tags:#code quality#testing#tdd#development workflow#refactoring#regression prevention
One-click install
npx skills add https://github.com/Tromml/kimchi --skill kimchi-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kimchi:tdd
Source: https://github.com/Tromml/kimchi/tree/main/plugins/kimchi/skills/tdd
Command: npx skills add https://github.com/Tromml/kimchi --skill kimchi-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all new code, bug fixes, and behavior changes are implemented following the Test-Driven Development (TDD) methodology, preventing regressions and improving code quality.

Core Features & Use Cases

  • Enforces TDD Cycle: Guides users through the RED-GREEN-REFACTOR process.
  • Prevents Regressions: Ensures fixes are testable and prevents future issues.
  • Use Case: Before implementing a new user authentication feature, use this Skill to write a failing test for the login process, then write the minimal code to pass, and finally refactor.

Quick Start

Use the kimchi:tdd skill to write a failing test for the new user registration endpoint.

Frequently Asked Questions about kimchi:tdd

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

FAQPage Schema
How do I enforce the Test-Driven Development cycle when implementing new features?▼

To enforce Test-Driven Development, you mandate the RED-GREEN-REFACTOR cycle for all code implementation, ensuring no production code is written without a preceding failing test to prevent regressions and improve code quality.

Why should I write a failing test before writing production code for bug fixes?▼

Writing a failing test before production code ensures your bug fixes are immediately testable and prevents future regressions. This RED-GREEN-REFACTOR methodology validates that the behavior change is correctly captured before implementation.

What is the best way to start TDD for a new user authentication feature?▼

The best way to start TDD for an authentication feature is writing a failing test for the login process first. You then write minimal code to pass the test, and finally refactor the implementation to complete the RED-GREEN-REFACTOR cycle.

Does the TDD RED-GREEN-REFACTOR methodology work for all software development tasks?▼

The TDD RED-GREEN-REFACTOR methodology is applicable to all software development tasks requiring behavioral implementation. It mandates the test-first cycle for any code implementation, bug fixes, or behavior changes to ensure robust code.

How do I prevent regressions when refactoring existing code behavior?▼

To prevent regressions during refactoring, you enforce a test-first workflow where a failing test precedes any behavior changes. This RED-GREEN-REFACTOR cycle ensures all refactoring is safely validated against established test cases.

Related Skills

Explore More Software Engineering Skills→
LucasSantana-DevLucasSantana-Dev
17

test-driven-development

Enforces Test-Driven Development workflow with Jest in Lucky's backend environment.

Community
Intermediate
CyapstayeCyapstaye
9

test-driven-development

Enforce the Red-Green-Refactor cycle with failing tests before implementation.

Community
Advanced
jrollinjrollin
2

tdd

Guide software implementation through the Red-Green-Refactor cycle.

Community
Advanced
GaryOcean428GaryOcean428

test-driven-development

Enforce Test-Driven Development by mandating failing tests before implementation code.

Community
Intermediate