skills.rest
Monjyu1101
Monjyu1101COMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce a red-green-refactor workflow requiring failing tests before code implementation.

1|Updated Jan 31, 2026
Search Tags:#tdd#red-green-refactor#unit-testing#software-quality#development-process#test-driven-development
One-click install
npx skills add https://github.com/Monjyu1101/AiDiy2026 --skill test-driven-development-monjyu1101
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/Monjyu1101/AiDiy2026/tree/main/backend_hermes/skills/software-development/test-driven-development
Command: npx skills add https://github.com/Monjyu1101/AiDiy2026 --skill test-driven-development-monjyu1101

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing code without tests is error-prone and hard to maintain; TDD enforces a discipline that ensures code quality by requiring tests before implementation.

Core Features & Use Cases

  • Red-Green-Refactor workflow that drives feature development and bug fixes with tests as the primary specification.
  • Test-first discipline that catches regressions early and documents intended behavior.
  • Use cases include adding new modules, refactoring with safety, and validating critical paths with automated tests.

Quick Start

Write a failing test for a new feature, then implement the minimal code to make it pass.

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 test-driven development for a new software feature?▼

To start test-driven development, write a failing unit test that defines the new feature's expected behavior. Then implement the minimal code necessary to make that failing test pass, ensuring the test acts as the primary specification.

What is the red-green-refactor workflow in unit testing?▼

The red-green-refactor workflow is a test-driven development process where you first write a failing test (red), implement the minimal code to make it pass (green), and then clean up the code without changing its behavior (refactor).

Why should I write tests before implementation code?▼

Writing tests before implementation enforces test-first discipline that catches regressions early and documents intended behavior. This approach ensures high software quality by requiring automated verification of failing tests before the actual code is written.

Can I use test-driven development for refactoring existing modules?▼

Yes, test-driven development supports refactoring existing modules with safety. By maintaining automated tests that verify critical paths, you can refactor code confidently knowing that any regression will be caught immediately by the test suite.

Does test-driven development work for fixing bugs in critical paths?▼

Test-driven development is highly effective for bug fixes in critical paths. You write a failing test that reproduces the specific bug, then implement the code fix until the test passes, ensuring the regression is permanently documented and prevented.

Related Skills

Explore More Software Engineering Skills→
anderskevanderskev
75

vitest-testing

Configure Vitest projects with unit and integration tests using mocking and snapshots.

Community
Intermediate
GainInsightDevGainInsightDev

af-analyse-test-coverage

Analyze test coverage reports to identify untested code paths and gaps.

Official
Intermediate
OvidOvid

writing-tests

Enforce a red-green-refactor workflow to reduce flaky tests across codebases.

Community
Intermediate
AnvinX1AnvinX1

tdd-workflow

Apply RED-GREEN-REFACTOR cycles with AAA test patterns for test-driven development.

Community
Intermediate