Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

test-driven-development

Estrellas92

Forks21

Actualizado12 de abril de 2026 a las 03:29

Drive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

KbWen

KbWen/agentic-os

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

Explorador de archivos

2 archivos

SKILL.md

readonly

name	test-driven-development
description	Drive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe.

Test-Driven Development

Overview

TDD uses the Red → Green → Refactor micro-cycle. First, define expected behavior. Next, use a minimal implementation to pass the test. Finally, organize the code structure.

When to Use

Adding or modifying core logic.
Fixing bugs and needing regression protection.
Requirements can be written as explicit input/output acceptance tests.

Workflow

Red: Write a failing test describing the expected behavior.
Green: Write the minimal code to make the test pass.
Refactor: Clean up naming, structure, and duplication.
Repeat the cycle until acceptance criteria are met.

Ironclad Rules

Do NOT write massive amounts of features before writing tests.
Focus on one small goal per cycle.
All tests MUST pass after refactoring.

Más de este repositorio

mismo repositorio

systematic-debugging

KbWen/agentic-os

Use 4-phase root cause analysis (Observe, Hypothesize, Verify, Fix); avoid unverified patches.

2026-07-0292

using-git-worktrees

KbWen/agentic-os

Use Git worktrees to create parallel working directories safely; avoid branch-switch contamination.

2026-06-2092

karpathy-principles

KbWen/agentic-os

Behavioral guidelines to reduce common LLM coding mistakes — Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution.

2026-06-1992

verification-before-completion

KbWen/agentic-os

Enforce "no evidence = no completion"; run Gate Function verification before declaring done.

2026-05-2692

production-readiness

KbWen/agentic-os

Pre-ship observability readiness checklist — ensures errors reach production monitoring, not just debug consoles.

2026-04-1692

red-team-adversarial

KbWen/agentic-os

Adversarial security and resilience analysis — auto-triggered during /review and /test based on task classification. Provides attack surface analysis, boundary testing, auth bypass attempts, dependency chain attacks, and Beast Mode stress testing.

2026-04-1692

name	test-driven-development
description	Drive changes with Red→Green→Refactor; ensure behavior is verifiable and regression-safe.

Test-Driven Development

Overview

TDD uses the Red → Green → Refactor micro-cycle. First, define expected behavior. Next, use a minimal implementation to pass the test. Finally, organize the code structure.

When to Use

Adding or modifying core logic.
Fixing bugs and needing regression protection.
Requirements can be written as explicit input/output acceptance tests.

Workflow

Red: Write a failing test describing the expected behavior.
Green: Write the minimal code to make the test pass.
Refactor: Clean up naming, structure, and duplication.
Repeat the cycle until acceptance criteria are met.

Ironclad Rules

Do NOT write massive amounts of features before writing tests.
Focus on one small goal per cycle.
All tests MUST pass after refactoring.