Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

test-driven-development

Étoiles92

Forks21

Mis à jour12 avril 2026 à 03:29

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

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

KbWen

KbWen/agentic-os

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

2 fichiers

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.

Plus depuis ce dépôt

même dépôt

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.