skills.rest
matsuyoshi30
matsuyoshi30COMMUNITY
Explore all skills by this author →
Website𝕏@matsuyoshi30GitHub

practicing-tdd-tidy-first

Automate TDD workflows with Red-Green-Refactor and Tidy First.

Updated Dec 15, 2019
Search Tags:#testing#tdd#red-green-refactor#plan.md#software-development#tidy-first#commit-discipline
One-click install
npx skills add https://github.com/matsuyoshi30/dotfiles --skill practicing-tdd-tidy-first
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: practicing-tdd-tidy-first
Source: https://github.com/matsuyoshi30/dotfiles/tree/main/.agents/skills/practicing-tdd-tidy-first
Command: npx skills add https://github.com/matsuyoshi30/dotfiles --skill practicing-tdd-tidy-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides developers through a disciplined TDD workflow (Red-Green-Refactor) and the Tidy First approach to ensure safe, incremental changes and clear commit history.

Core Features & Use Cases

  • TDD cycle: Red, Green, Refactor with minimal production code to move features forward.
  • Tidy First discipline: Separate structural changes from behavioral changes to keep commits focused.
  • Plan-driven loop (optional): If a plan.md exists, treat it as the source of truth for the next test and work through it deterministically.

Quick Start

Start by checking for a plan.md and following the next unmarked test; implement the test to fail, write only enough production code to pass, and refactor while keeping all tests green, then commit as a single logical unit.

Frequently Asked Questions about practicing-tdd-tidy-first

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

FAQPage Schema
How do I separate structural changes from behavioral changes in TDD?▼

Tidy First discipline separates structural changes from behavioral changes during the Red-Green-Refactor cycle to keep commits focused and ensure safe, incremental software development.

What is the best way to enforce one-test-at-a-time increments in TDD?▼

A plan-driven loop using a plan.md file as the source of truth enforces one-test-at-a-time increments, ensuring you work through the next unmarked test deterministically during TDD.

How does Tidy First improve commit discipline in software development?▼

Tidy First improves commit discipline by separating structural refactoring from behavioral changes, ensuring commits are small, traceable, and represent a single logical unit of work.

When should I use a plan.md file for TDD workflows?▼

Use a plan.md file when starting new features or repairing bugs to treat it as the source of truth for the next test, guiding your TDD workflow deterministically through unmarked tests.

Does Tidy First work with standard Red-Green-Refactor testing cycles?▼

Tidy First integrates directly with Red-Green-Refactor cycles, applying when starting new features or repairing bugs across projects that explicitly separate structural from behavioral changes.

Why do my TDD commits end up too large and unfocused?▼

Failing to separate structural changes from behavioral changes causes unfocused commits; applying Tidy First discipline ensures refactoring stays distinct from feature behavior increments.

Related Skills

Explore More Software Engineering Skills→
rochaluiz8888rochaluiz8888

conductor

Enforce plan.md-driven lifecycle governance with conventional commits and TDD cycles.

Community
Advanced
ssiumhassiumha
9

tdd-practices

Guide developers through the RED-GREEN-REFACTOR TDD cycle.

Community
Advanced
craigtkhillcraigtkhill

test-driven-development

Enforce the RED-GREEN-REFACTOR test cycle across software projects.

Community
Intermediate
datamaker-krdatamaker-kr
1

tdd-workflow

Guide development through Red-Green-Refactor cycles and Tidy First principles.

Official
Intermediate