Run any Skill in Manus with one click

tdd-red-green-refactor

Stars0

Forks0

UpdatedMay 20, 2026 at 20:18

Execute a minimal-scope red-green-refactor workflow. Use for test-first features, regression-first bug fixes, and refactors that must preserve externally observable behavior.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

kwkraus

kwkraus/edgefront-builder

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	tdd-red-green-refactor
description	Execute a minimal-scope red-green-refactor workflow. Use for test-first features, regression-first bug fixes, and refactors that must preserve externally observable behavior.
argument-hint	Describe the requested behavior, target component, test-first constraints, and any limits on refactoring scope.

TDD Red Green Refactor

When to Use

New behavior implementation requiring test-first workflow
Bug fixes that need regression-first coverage
Refactors that must preserve externally observable behavior

Quick Checklist

Write a failing test for requested behavior.
Implement the smallest change to make it pass.
Refactor only where needed for clarity/maintainability.
Re-run focused verification and report outcomes.

Deep Workflow

Define acceptance behavior in one sentence and convert it to a focused failing test.
Confirm the test fails for the expected reason before changing production code.
Implement minimal production changes to satisfy the failing test.
Re-run focused tests; if passing, perform constrained refactor that preserves behavior.
Re-run tests after refactor and broaden verification only when risk indicates.
Report red/green evidence, refactor scope, and residual risks.

Decision Points

If multiple failures appear, isolate the smallest deterministic failure first.
If passing requires broad code movement, split work and keep the first change minimal.
If bug fix is requested, require a regression test that fails before the fix.

Completion Checks

A failing test existed before implementation.
Production change is minimal and traceable to test intent.
Refactor does not alter externally observable behavior.
Focused verification passes for touched scope.

More from this repository

same repository

api-contract-design

kwkraus/edgefront-builder

Design ASP.NET Core minimal API request and response contracts. Use for DTO shapes, route and verb decisions, OpenAPI metadata, and compatibility planning before implementation.

2026-05-200

api-test-strategy

kwkraus/edgefront-builder

Define focused tests for ASP.NET Core minimal APIs. Use for endpoint branch coverage, contract assertions, regression planning, and choosing the narrowest useful verification command.

2026-05-200

data-schema-migration

kwkraus/edgefront-builder

Design EF Core schema changes, constraints, and migrations for the backend data model. Use for entity updates, indexes, uniqueness rules, cascade behavior, and migration planning.

2026-05-200

delegated-data-sync-pipeline

kwkraus/edgefront-builder

Design and implement the delegated Graph sync pipeline from fetch through normalization, upsert, and metrics recompute. Use for user-initiated registrations or attendance sync, idempotency, and atomic recomputation.

2026-05-200

deployment-safety-and-rollback

kwkraus/edgefront-builder

Define deployment safeguards, environment protections, and rollback readiness for CI/CD releases. Use when adding or reviewing release jobs, promotion controls, or recovery plans.

2026-05-200

domain-metrics-computation

kwkraus/edgefront-builder

Apply email and domain normalization plus session and series metric rules, including W1/W2 warm-account logic and internal-domain exclusion. Use for domain logic changes, recompute behavior, and mandatory unit-test coverage.

2026-05-200

name	tdd-red-green-refactor
description	Execute a minimal-scope red-green-refactor workflow. Use for test-first features, regression-first bug fixes, and refactors that must preserve externally observable behavior.
argument-hint	Describe the requested behavior, target component, test-first constraints, and any limits on refactoring scope.

TDD Red Green Refactor

When to Use

New behavior implementation requiring test-first workflow
Bug fixes that need regression-first coverage
Refactors that must preserve externally observable behavior

Quick Checklist

Write a failing test for requested behavior.
Implement the smallest change to make it pass.
Refactor only where needed for clarity/maintainability.
Re-run focused verification and report outcomes.

Deep Workflow

Define acceptance behavior in one sentence and convert it to a focused failing test.
Confirm the test fails for the expected reason before changing production code.
Implement minimal production changes to satisfy the failing test.
Re-run focused tests; if passing, perform constrained refactor that preserves behavior.
Re-run tests after refactor and broaden verification only when risk indicates.
Report red/green evidence, refactor scope, and residual risks.

Decision Points

If multiple failures appear, isolate the smallest deterministic failure first.
If passing requires broad code movement, split work and keep the first change minimal.
If bug fix is requested, require a regression test that fails before the fix.

Completion Checks

A failing test existed before implementation.
Production change is minimal and traceable to test intent.
Refactor does not alter externally observable behavior.
Focused verification passes for touched scope.