skills.rest
davpatel605-beep
davpatel605-beepCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce a RED-GREEN-REFACTOR workflow with failing tests before production code.

Updated Jun 25, 2026
Search Tags:#testing#tdd#quality assurance#unit testing#software development#red-green-refactor
One-click install
npx skills add https://github.com/davpatel605-beep/hermusagent --skill test-driven-development-davpatel605-beep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/davpatel605-beep/hermusagent/tree/main/backend/vendor/hermes/skills/software-development/test-driven-development
Command: npx skills add https://github.com/davpatel605-beep/hermusagent --skill test-driven-development-davpatel605-beep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unreliable software changes by enforcing a disciplined test-first workflow that verifies behavior before implementation and reduces regressions.

Core Features & Use Cases

  • RED-GREEN-REFACTOR Workflow: Guides developers through writing failing tests, implementing minimal solutions, and safely improving code.
  • Test Quality Enforcement: Promotes behavior-focused tests, validation of failures, and avoidance of brittle implementation-specific testing.
  • Use Case: Apply this Skill when building new features, fixing bugs, or refactoring code to ensure every change is backed by verified tests.

Quick Start

Use the test-driven-development skill to implement this feature by writing a failing test first, making it pass with minimal code, and then refactoring safely.

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 workflow in test-driven development?▼

The red-green-refactor workflow in test-driven development involves writing a failing test, implementing minimal code to pass it, and safely refactoring. This cycle enforces test-first discipline to verify behavior before production code is written.

How do I write unit tests before implementing a new feature?▼

To write unit tests before a feature, start by creating a failing test that defines the desired behavior, implement the minimal solution to make it pass, and then refactor. This ensures every change is backed by verified tests.

When should I apply test-first discipline during software development?▼

Apply test-first discipline during feature development, bug fixes, refactoring tasks, and behavior changes. It is needed whenever you want to prevent regressions and ensure software reliability through validated, behavior-focused testing.

How do I avoid brittle implementation-specific tests in TDD?▼

To avoid brittle implementation-specific tests in TDD, focus on validating behavior rather than internal code structures. The workflow enforces behavior-focused test practices and verifies actual failures to prevent unreliable software changes.

Does test-driven development work for fixing bugs and refactoring existing code?▼

Yes, test-driven development works for bug fixes and refactoring existing code. It enforces writing failing tests that capture the current issue or desired behavior, ensuring changes are validated and regressions are prevented.

Related Skills

Explore More Software Engineering Skills→
AvatarGanymedeAvatarGanymede

tdd

Automate Test-Driven Development cycles with failing tests before production code.

Community
Intermediate
CyapstayeCyapstaye
9

test-driven-development

Enforce the Red-Green-Refactor cycle with failing tests before implementation.

Community
Advanced
zinohomezinohome

test-driven-development

Enforce test-first development with red-green-refactor cycles and automated test coverage.

Community
Intermediate
AsiaOstrichAsiaOstrich
70

ATDD 助手

Guide teams through ATDD workflows with Given-When-Then acceptance criteria.

Community
Intermediate