Enforce a RED-GREEN-REFACTOR cycle for behavior-changing code.
npx skills add https://github.com/kanade0404/dotfiles --skill tdd-kanade0404
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/kanade0404/dotfiles/tree/main/.opencode/skills/tdd Command: npx skills add https://github.com/kanade0404/dotfiles --skill tdd-kanade0404
This Skill prevents behavior changes from being coded before they are specified by a failing test, reducing regressions and keeping implementation aligned with intended behavior.
Use the tdd skill to add one behavior by writing a failing test first, then implementing the smallest fix, and finally refactoring while keeping all tests green.
High-intent search queries and answers about installing and using this skill.
Test-first development for bug fixes and new features is enforced by writing a failing test that specifies the intended behavior before any implementation code is written. This ensures the smallest fix is applied only after verifying a genuine test failure.
The red-green-refactor cycle in unit testing is a strict development loop where you write a failing test, implement the smallest code to make it pass, and then refactor while keeping all tests green. It enforces behavior verification one cycle at a time.
To distinguish real test failures from setup problems during test-first development, the process rejects false-red setup failures and halts development if the test fails due to environmental issues rather than the intended behavior change.
Yes, test-first development applies to API behavior changes and integration workflows by requiring a verified failing test before altering any observable program behavior in both unit and integration workflows.
The best way to prevent regressions when changing observable program behavior is to preserve existing passing tests while enforcing a strict test-first cycle, ensuring implementation aligns completely with the newly specified behavior.
A strict red-green-refactor cycle should not be used when a request does not alter observable program behavior in unit or integration workflows, as it is specifically designed to enforce behavior-changing code through verified failing tests.
bonnguyenitcEnforce test-first development with failing tests before production code.
CyapstayeEnforce the Red-Green-Refactor cycle with failing tests before implementation.
DIO0550Define a Red-Green-Refactor TDD workflow for Rust projects with cargo test verification.
AcidicSoilImplement task specifications via TDD Red-Green-Refactor cycles with tests and telemetry.
