How does the Red/Green/Verify cycle work in this skill?

It follows a three-step process: first, write a failing test and a minimal stub; second, write only the code necessary to make that test pass; third, run quality checks like linting to verify the code meets standards.

How does it prevent over-engineering?

The skill enforces a rule to stop writing code as soon as a test passes and prohibits creating helper functions unless they are immediately required by a currently failing test.

Does this skill require full test coverage immediately?

No, it focuses on the 'happy path' and obvious error cases during the development phase to maintain momentum, allowing for exhaustive coverage gaps to be closed in a later release phase.

Can I use this for existing codebases?

Yes, the skill is designed to integrate into existing projects by utilizing standard commands like 'make check' and 'make lint' to verify implementation changes.

Test-Driven Development (TDD)

Name: Test-Driven Development (TDD)
Author: mgreenly

bymgreenly

•

Security & Testing

Implements a disciplined Red-Green-Verify development cycle to ensure high-quality, test-backed code implementation.

About

The TDD skill provides a structured framework for Test-Driven Development within the Ikigai ecosystem, guiding Claude to prioritize testing before implementation. By enforcing the Red/Green/Verify cycle, it ensures that every piece of code is justified by a failing test and meets quality standards through automated linting and complexity checks. This skill is particularly useful during the active development phase to maintain momentum while building a robust foundation of unit tests for the 'happy path' and obvious error conditions.

Key Features

Strict Red/Green/Verify workflow enforcement
Integrated quality checks using make check and make lint
Focused development on happy-path and primary error cases
Minimalist code implementation to prevent over-engineering
Failing test stub generation for C-style headers and implementations
1 GitHub stars

Use Cases

Refactoring existing codebases while ensuring functional correctness
Maintaining high code quality and low complexity during rapid development
Implementing new project features with a test-first methodology

About

Key Features

Strict Red/Green/Verify workflow enforcement
Integrated quality checks using make check and make lint
Focused development on happy-path and primary error cases
Minimalist code implementation to prevent over-engineering
Failing test stub generation for C-style headers and implementations
1 GitHub stars

Use Cases

Refactoring existing codebases while ensuring functional correctness
Maintaining high code quality and low complexity during rapid development
Implementing new project features with a test-first methodology