skills.rest
markwang2658
markwang2658COMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforces RED-GREEN-REFACTOR cycles by requiring a failing test before production code.

31|3|Updated May 7, 2026
Search Tags:#tdd#refactoring#red-green-refactor#code-quality#unit-testing#test-driven-development
One-click install
npx skills add https://github.com/markwang2658/hermes-windows-native --skill test-driven-development-markwang2658
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/markwang2658/hermes-windows-native/tree/main/hermes-agent/skills/software-development/test-driven-development
Command: npx skills add https://github.com/markwang2658/hermes-windows-native --skill test-driven-development-markwang2658

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the discipline of writing tests before production code, reducing regressions and improving long-term maintainability.

Core Features & Use Cases

  • Enforces the RED-GREEN-REFACTOR workflow by guiding users to write failing tests first, implement minimal production code to pass, and refactor with confidence.
  • Promotes test naming conventions, incremental design, and faster feedback cycles across software projects.
  • Use Case: A developer adds a new feature; they write a failing test, implement just enough code to pass, and then refactor while keeping all tests green.

Quick Start

Write a failing test for the desired behavior, then implement the minimal code to pass and refactor.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
What is the red-green-refactor cycle in test-driven development?▼

Test-driven development enforces writing a failing test before production code, implementing only enough logic to pass, and refactoring safely. This discipline reduces regressions and improves long-term maintainability across software projects.

How do I write unit tests before implementing new features?▼

To write unit tests before new features, start by defining desired behavior with a failing test, implement the minimal code required to turn it green, and then refactor incrementally. This ensures faster feedback cycles and structured design.

Does test-driven development work for bug fixes and code refactoring?▼

Test-driven development works for bug fixes and refactoring by guiding engineers to write failing tests that capture the bug or desired behavior, implementing minimal code to pass, and refactoring with confidence while maintaining a green test suite.

Can I apply test-first development across different programming languages?▼

Test-first development applies across software projects and languages without specific dependencies. It guides engineers through disciplined workflows with clear test naming and minimal production code, independent of the underlying technology stack.

When should I not use test-driven development for unit testing?▼

Test-driven development may be less suitable for exploratory prototyping where desired behavior is undefined. It requires clear test naming and incremental design, making it less efficient if exact functional requirements are unstable.

Related Skills

Explore More Software Engineering Skills→
timbuchingertimbuchinger
1

test-driven-development

Enforce writing failing tests before implementing minimal code to pass.

Community
Basic
haakonbullhaakonbull
5

test-refactoring

Refactor Python pytest suites by merging overlaps, parameterizing duplicates, and pruning dead coverage.

Community
Intermediate
knckknckknckknck

go-style-guide

Standardize Go code quality and style across projects.

Community
Intermediate
pgm1980pgm1980

test-driven-development

Guide test-first software changes through a Red-Green-Refactor loop.

Community
Intermediate