skills.rest
darthlinuxer
darthlinuxerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-driven-development

Guide software development through the RED-GREEN-REFACTOR test-first cycle.

1|1|Updated Feb 4, 2026
Search Tags:#TDD#refactoring#patterns#unit-testing#software-quality#test-driven-development#RED-GREEN-REFACTOR
One-click install
npx skills add https://github.com/darthlinuxer/Agentic-Skills --skill test-driven-development-darthlinuxer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/darthlinuxer/Agentic-Skills/tree/main/test-driven-development
Command: npx skills add https://github.com/darthlinuxer/Agentic-Skills --skill test-driven-development-darthlinuxer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams implement features and fix bugs using a strict test-first workflow (RED-GREEN-REFACTOR) guided by senior-software-developer patterns.

Core Features & Use Cases

  • Enforces a test-first cycle (RED-GREEN-REFACTOR) to drive design and refactoring.
  • Provides language-agnostic patterns for code quality and reliable verification.
  • Use Case: For a single-task feature, write a failing test first, implement minimally to pass, then refactor while keeping tests green.

Quick Start

  • Write a failing test that captures the intended behavior.
  • Implement just enough code to make the test pass.
  • Refactor the codebase to improve clarity and remove duplication, keeping all tests green.

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?▼

The RED-GREEN-REFACTOR cycle in test-driven development involves writing a failing test, implementing minimal code to pass, and refactoring to improve clarity while keeping tests green.

How do I start writing unit tests before implementing a feature?▼

Start writing unit tests by capturing the intended behavior in a failing test, implement just enough code to pass, then refactor to remove duplication while maintaining green tests.

Can I use test-driven development for multi-step software projects?▼

Test-driven development is designed for single-task feature development and bug fixes. Multi-step projects require explicit guidance to use writing-plans and subagent-driven-development workflows.

Does test-driven development provide language-specific refactoring patterns?▼

Test-driven development provides language-agnostic patterns for code quality and reliable verification, guiding systematic refactoring across different programming languages.

Why should I write a failing test first during bug fixes?▼

Writing a failing test first during bug fixes ensures systematic verification of the failure, enables minimal implementation to fix it, and supports refactoring while keeping tests green.

Related Skills

Explore More Software Engineering Skills→
AztecProtocolAztecProtocol
449

unit-test-implementation

Implement unit tests in a TypeScript monorepo with Jest.

Official
Intermediate
ChimeraFoundationaChimeraFoundationa

writing-plans

Draft end-to-end implementation plans with tasks, file paths, code, and testing steps.

Community
Advanced
AdemKaoAdemKao

feature-implementation

Coordinate end-to-end feature delivery using a BDD/TDD workflow blueprint.

Community
Advanced
grasberggrasberg
3

tdd-workflow

Enforce a RED-GREEN-REFACTOR test-first workflow with AAA patterns.

Community
Intermediate