common-tdd

Enforce Test-Driven Development workflows requiring failing tests before production code.

Updated Jun 25, 2026

Search Tags:#tdd #test automation #unit testing #test-driven development #red-green-refactor

Ready to run

npx skills add https://github.com/VSF-QC-TTS/vf-qc-copilot --skill common-tdd-vsf-qc-tts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: common-tdd
Source: https://github.com/VSF-QC-TTS/vf-qc-copilot/tree/main/.agents/skills/common/common-tdd
Command: npx skills add https://github.com/VSF-QC-TTS/vf-qc-copilot --skill common-tdd-vsf-qc-tts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces a strict Test-Driven Development (TDD) workflow, ensuring no production code is written without a prior failing test, which improves code quality and maintainability.

Core Features & Use Cases

Enforce TDD Practices: Follows the Red-Green-Refactor loop, promoting good coding habits.
File Triggering: Triggered by changes to specific test files, ensuring timely testing.
Keyword Matching: Responds to keywords related to TDD and testing, making it accessible and actionable.

Quick Start

Enable the common-tdd skill and start writing your next test in any supported test file format.

Frequently Asked Questions about common-tdd

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

FAQPage Schema

How do I enforce test-driven development in my workflow so no production code is written without a failing test?▼

Test-driven development is enforced by applying the strict Red-Green-Refactor loop, which requires all production code to be written against a prior failing test. This approach improves code quality and maintainability across new feature development and bug fixing.

What is the Red-Green-Refactor loop in unit testing and how does it structure test creation?▼

The Red-Green-Refactor loop in unit testing requires writing a failing test first, writing production code to pass it, and then refactoring. It enforces the Arrange-Act-Assert structure and TDD best practices to expand test coverage.

Can I trigger test automation automatically when I modify specific test files?▼

Test automation can be triggered by changes to specific test files. The workflow responds to file modifications and matches keywords related to test-driven development, ensuring timely testing during development.

Does strict test-driven development work for both bug fixing and new feature development?▼

Test-driven development works for both bug fixing and new feature development. It requires adherence to the Arrange-Act-Assert structure and coverage thresholds, applying TDD best practices across various programming workflows.

What's the best way to expand test coverage thresholds using TDD best practices?▼

The best way to expand test coverage thresholds is by following the strict Red-Green-Refactor loop with the Arrange-Act-Assert structure. This ensures no production code exists without prior failing tests, meeting coverage requirements.