skills.rest
russosalv
russosalvCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce a red-green-refactor workflow with failing tests before production code.

5|Updated Apr 18, 2026
Search Tags:#unit tests#testing#tdd#refactoring#red-green-refactor#test-first#test-driven-development
One-click install
npx skills add https://github.com/russosalv/NONoise --skill test-driven-development-russosalv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/vendor/superpowers/skills/test-driven-development
Command: npx skills add https://github.com/russosalv/NONoise --skill test-driven-development-russosalv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents shipping untested production code by enforcing a test-first workflow that proves desired behavior before implementation, reducing regressions and increasing confidence during change.

Core Features & Use Cases

  • Red-Green-Refactor cycle: Guide to write a minimal failing test, implement the smallest change to pass, then safely refactor.
  • Verification gates: Explicit checks to confirm tests fail for the right reason, pass when implemented, and keep the suite green after refactors.
  • Use cases: New feature development, bug fixes, refactors, and behavioral changes where automated tests are required as the source of truth.

Quick Start

Write a failing unit test that reproduces the desired behavior for the new feature, then implement the minimal code to make the test pass and confirm all tests remain green.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I start writing unit tests before production code?▼

The red-green-refactor cycle enforces test-driven development by having you write a minimal failing test, implement the smallest code change to pass it, then safely refactor while keeping all tests green.

Why does test-driven development require verifying expected failures first?▼

Verifying expected failures first ensures the test fails for the right reason, proving the desired behavior is absent before writing minimal production code to pass it.

When should I use test-first workflows for bug fixes and refactoring?▼

Use test-first workflows for bug fixes and refactoring when automated tests must prove behavior before implementation, reducing regressions and increasing confidence during code changes.

Does test-driven development work for new feature development and behavior changes?▼

Yes, test-driven development applies to new feature development, bug fixes, refactors, and behavior changes where automated tests serve as the source of truth for correct behavior.

How do I keep my test suite green during refactoring?▼

To keep your test suite green during refactoring, implement minimal fixes to pass tests first, then apply safe refactors while running explicit verification gates to confirm all tests remain green.

Related Skills

Explore More Software Engineering Skills→
timbuchingertimbuchinger
1

test-driven-development

Enforce writing failing tests before implementing minimal code to pass.

Community
Basic
CodingCossackCodingCossack
19

test-driven-development

Enforce a test-first workflow with failing tests before production code.

Community
Intermediate
peopleforresterpeopleforrester
3

refactoring-guide

Restructures code safely while preserving visible behavior through defined, testable steps.

Community
Basic
alexfalkowskialexfalkowski
2

testing-standards

Enforce behavior-driven development and repository-defined test harnesses across unit, integration, and feature tests.

Community
Advanced