skills.rest
SAZO-KR
SAZO-KROFFICIAL
Explore all skills by this author →
WebsiteGitHub

develop

Automate test-driven development workflows with red-green-refactor and structured commits.

Updated Jan 2, 2026
Search Tags:#testing#tdd#red-green-refactor#bugfix#feature-development#commit-discipline
One-click install
npx skills add https://github.com/SAZO-KR/sazo-toolkit --skill develop-sazo-kr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: develop
Source: https://github.com/SAZO-KR/sazo-toolkit/tree/main/packages/ai-harness/skills/develop
Command: npx skills add https://github.com/SAZO-KR/sazo-toolkit --skill develop-sazo-kr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, test-first workflow to guide developers through feature implementation and bug fixes, reducing regressions and fostering clean, incremental progress.

Core Features & Use Cases

  • Red → Green → Refactor discipline embedded in daily practice.
  • Test Type Decision Gate to classify tasks as unit, integration, or boundary tests before coding.
  • One failing test at a time with minimal, incremental code changes.
  • Two-commit approach: structural changes separate from behavioral changes.
  • Structured commit discipline and Tidy First to improve maintainability and reproducibility.
  • Use across feature development, bug fixes, or refactoring tasks.

Quick Start

Identify a small feature, write one failing test, run tests to turn RED, implement the minimal code to turn GREEN, and commit the change as a distinct structural or behavioral increment.

Frequently Asked Questions about develop

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

FAQPage Schema
How do I structure test-driven development workflows for feature development and bug fixes?▼

Test-driven development workflows are structured by enforcing a red-green-refactor cycle, writing one failing test at a time, and making minimal incremental code changes to pass. This reduces regressions and fosters clean progress across feature work and bug fixes.

What is the best way to separate structural and behavioral changes in TDD commits?▼

Separating structural and behavioral changes in TDD commits requires a two-commit approach guided by Tidy First principles. You commit structural code adjustments distinctly from behavioral changes to improve maintainability and reproducibility.

How do I decide between unit, integration, or boundary tests before coding?▼

You decide between unit, integration, or boundary tests before coding by using a Test Type Decision Gate. This mechanism classifies the specific task upfront, ensuring the correct test scope is applied before implementation begins.

Can I use a structured red-green-refactor cycle for refactoring tasks?▼

Yes, you can use a structured red-green-refactor cycle for refactoring tasks. The workflow operates across feature development, bug fixes, and refactoring cycles, maintaining structured commit discipline and incremental test progression throughout.

Why write one failing test at a time during feature development?▼

Writing one failing test at a time during feature development enforces disciplined test progression and minimal code implementation. This approach turns the test RED, allows minimal code to turn it GREEN, and reduces regressions by isolating changes.

Related Skills

Explore More Software Engineering Skills→
camoneartcamoneart
5

Practicing TDD

Guide developers through Red-Green-Refactor cycles with test-first workflows.

Community
Basic
yocxy2yocxy2

land-and-deploy

Merge pull requests and verify production deployment health with canary checks.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
johannesfritzjohannesfritz
1

integration-testing

Run integration tests across services to validate end-to-end behavior.

Community
Advanced