test-driven-development

Enforce a red-green-refactor workflow for writing tests before code.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/cyalcala/va-freelance-hub --skill test-driven-development-cyalcala
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/cyalcala/va-freelance-hub/tree/main/.antigravity/skills_old_tainted/test-driven-development
Command: npx skills add https://github.com/cyalcala/va-freelance-hub --skill test-driven-development-cyalcala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drives development by ensuring tests are written before code, making bugs easier to reproduce and fixes safer.

Core Features & Use Cases

  • Enforces a red-green-refactor workflow for new features and bug fixes.
  • Encourages writing reproduction tests for bug reports and changes, improving reliability.
  • Provides guidance on test structure and quality best practices (DAMP, flaky test avoidance, meaningful names).

Quick Start

Write a failing test before writing the code that makes 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 writing tests before implementing code for new features?

To practice test-driven development, write a failing test before writing the code that makes it pass. This enforces a red-green-refactor workflow, ensuring bugs are easier to reproduce and fixes are safer across software projects.

What is the red-green-refactor workflow in software engineering?

The red-green-refactor workflow is a test-driven development process where you write a failing test, implement code to make it pass, and then refactor. It drives development by ensuring tests are written before code for new features and bug fixes.

How do I write a reproduction test for a bug report?

Write a failing reproduction test that captures the reported bug before changing any existing behavior. This test-driven approach makes bugs easier to reproduce and ensures your subsequent code fixes are safer and validated by the failing test turning green.

What are the best practices for test structure and maintainability?

Best practices for test quality include following DAMP principles, avoiding flaky tests, and using meaningful test names. This ensures your test-driven development process remains maintainable and reliable across new feature work and bug fixes.

Can I use test-driven development for fixing bugs and changing existing behavior?

Yes, test-driven development is applicable during bug fixes and changes to existing behavior. You enforce a red-green-refactor workflow by writing a reproduction test for the bug first, ensuring the fix is validated before the code is implemented.

Why should I write a failing test before writing the code that makes it pass?

Writing a failing test first drives quality by making bugs easier to reproduce and fixes safer. This test-driven development approach ensures your code directly satisfies test requirements and maintains structural quality across software projects.