skills.rest
arthrod
arthrodCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforce a red-green-refactor test-driven development workflow for software tasks.

Updated Jul 18, 2026
Search Tags:#testing#tdd#debugging#refactoring#unit-testing#software-quality
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill test-driven-development-arthrod
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/arthrod/conejo-skills --skill test-driven-development-arthrod

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the technical debt and uncertainty caused by writing code before tests, ensuring every feature is verified by a failing test before implementation.

Core Features & Use Cases

  • Red-Green-Refactor Enforcement: Mandates the complete TDD cycle to ensure code quality and prevent regressions.
  • Anti-Pattern Detection: Provides strict guidelines to avoid common testing pitfalls like mocking behavior instead of real logic.
  • Use Case: When implementing a complex feature, use this skill to define the expected behavior through a failing test, write the minimal code to pass, and safely refactor without breaking existing functionality.

Quick Start

Activate the test-driven-development skill to begin a new feature implementation by writing a failing test first.

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I enforce strict test-driven development for reliable software engineering?▼

Apply the test-driven development red-green-refactor cycle to implement features, bug fixes, and refactoring. Write a failing test defining expected behavior, write minimal code to pass it, then safely refactor without breaking functionality.

How do I write a failing test before implementing production code?▼

Apply the test-driven development red-green-refactor cycle to implement features, bug fixes, and refactoring. Write a failing test defining expected behavior, write minimal code to pass it, then safely refactor without breaking functionality.

What is the red-green-refactor cycle for unit testing?▼

The red-green-refactor cycle in unit testing requires writing a failing test first, implementing the minimal code to make it pass, and then safely refactoring. This workflow eliminates uncertainty and prevents regressions.

Does test-driven development help with safe code refactoring?▼

Test-driven development enables safe refactoring by ensuring existing functionality is verified by preceding tests. You can safely refactor code without breaking existing features because the tests validate expected behavior.

What are common anti-patterns to avoid in test-driven development?▼

Common test-driven development anti-patterns include mocking behavior instead of testing real logic. Strict guidelines help avoid these testing pitfalls to ensure code quality and prevent regressions during feature implementation.

Can I use test-driven development for bug fixes and refactoring efforts?▼

Test-driven development applies to all bug fixes and refactoring efforts, not just new features. It requires adherence to the strict red-green-refactor cycle to ensure high code reliability throughout the software engineering process.

Related Skills

Explore More Software Engineering Skills→
DanomanicDanomanic

tdd-approach

Enforce red-green-refactor cycles with failing tests before implementation.

Community
Intermediate
channingwaltonchanningwalton
3

Refactor

Refactor code incrementally while preserving behavior and passing tests.

Community
Advanced
farmountainfarmountain
1

Refactor Agent

Detect code smells and apply incremental refactorings with test coverage.

Community
Advanced
diegoknskdiegoknsk

testing

Standardizes .NET testing with xUnit, Moq, SpecFlow, and CI/CD workflows.

Community
Advanced