skills.rest
zagarlucas
zagarlucasCOMMUNITY
Explore all skills by this author →
GitHub

tdd-strict

Enforce strict Test-Driven Development workflows with RED, GREEN, REFACTOR cycles.

Updated Jan 27, 2026
Search Tags:#testing#tdd#red-green-refactor#best-practices#software-quality#code-review#unit-tests
One-click install
npx skills add https://github.com/zagarlucas/zagarlucas.github.io --skill tdd-strict-zagarlucas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-strict
Source: https://github.com/zagarlucas/zagarlucas.github.io/tree/main/.continue/skills/tdd-strict
Command: npx skills add https://github.com/zagarlucas/zagarlucas.github.io --skill tdd-strict-zagarlucas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diese Skill zwingt Entwickler, Tests vor Implementierung zu schreiben und blockiert Code-Generierung ohne vorherige Tests. Er dokumentiert 13 ungueltige Rationalisierungen und fördert konsequente TDD-Praktiken.

Core Features & Use Cases

  • Strikte Red-Green-Refactor-Zyklen, die sicherstellen, dass Tests zuerst existieren und Funktionsverhalten validieren.
  • Erkennung und Vermeidung von verbreiteten TDD-Rouges wie "Tests nach Code" oder "Spaeter testen".
  • Geeignet für neue Features, Bugfixes und Refactoring, sowie API-Erweiterungen, um Regressionen zu verhindern.

Quick Start

Schreibe zuerst einen fehlgeschlagenen Test, bevor du Code schreibst, und folge der Red-Green-Refactor-Abfolge.

Frequently Asked Questions about tdd-strict

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

FAQPage Schema
How do I enforce strict test-driven development workflows for new features?▼

To enforce strict test-driven development, you must write a failing unit test before any implementation code, then follow the RED, GREEN, REFACTOR sequence. This workflow blocks code generation without tests and validates feature behavior comprehensively.

What are common TDD anti-patterns and rationalizations to avoid during refactoring?▼

Common TDD anti-patterns include rationalizations like writing tests after code or postponing testing until later. Avoiding these rouges ensures you maintain valid RED, GREEN, REFACTOR cycles and prevent regressions during refactoring and bug fixes.

Can I use strict TDD practices for both bug fixes and API extensions?▼

Yes, you can apply strict TDD practices to bug fixes, refactoring, and API extensions. Identifying or creating tests before code validates functional behavior and prevents regressions across all software engineering tasks.

Why does strict TDD block code generation without previous unit tests?▼

Strict TDD blocks code generation without previous unit tests to prevent unvalidated implementations and ensure functional behavior is specified first. This mitigates common anti-patterns and maintains software quality.

What is the best way to start a Red-Green-Refactor cycle for unit tests?▼

The best way to start a Red-Green-Refactor cycle is to write a failing unit test first, before writing any implementation code. This ensures the test validates the desired behavior and guides the development process safely.

Related Skills

Explore More Software Engineering Skills→
OutlineDrivenOutlineDriven
5

test-driven

Define and apply test-driven development practices across programming languages.

Official
Intermediate
redhat-developerredhat-developer
170

e2e-verify-fix

Verify Playwright end-to-end test fixes with repeated runs and code quality checks.

Official
Advanced
jorgeasaurusjorgeasaurus
12

writing-hookify-rules

Configure hookify rules with regex patterns to enforce code security best practices.

Community
Intermediate
chichexchichex
2

sdd-init

Generate a verifiable project contract defining build, test, and maintenance commands.

Community
Advanced