tdd-workflow

Enforces test-driven development workflows with Git checkpoints and 80% minimum coverage.

Updated May 9, 2026
One-click install
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill tdd-workflow-kk20300113-png
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/tdd-workflow
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill tdd-workflow-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of shipping untested code that causes production bugs, makes refactoring dangerous, and leads to unreliable software releases.

Core Features & Use Cases

  • End-to-End TDD Enforcement: Guides you to write failing tests first, implement minimal code to pass them, then refactor, following strict RED-GREEN-REFACTOR cycles.
  • Comprehensive Coverage Requirements: Mandates 80%+ test coverage across unit, integration, and end-to-end tests, with guidance for mocking external services like Supabase, Redis, and OpenAI.
  • Git Checkpoint Guidance: Provides clear rules for creating Git commits at each TDD stage to track progress and validate test states.
  • Use Case: When building a new user authentication API, this Skill ensures you write failing integration tests for login and signup flows first, implement the endpoint to pass all tests, and verify coverage meets the threshold before merging.

Quick Start

Use the tdd-workflow skill to implement the new payment processing feature following test-driven development principles with full test coverage.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce test-driven development workflows for full-stack code changes?

Enforce test-driven development workflows by applying strict RED-GREEN-REFACTOR cycles to all code changes, ensuring you write failing tests first, implement minimal code to pass them, then refactor to eliminate untested code risks.

What is the minimum code coverage required for unit and integration tests in TDD?

Minimum code coverage required for test-driven development is 80 percent across unit tests for components, integration tests for APIs and database operations, and end-to-end tests for critical user flows.

How do I create Git checkpoints during each test-driven development stage?

Create Git checkpoints during test-driven development by committing your code at each TDD stage, which tracks progress and validates test states before merging new features, bug fixes, or refactors.

Can I use standardized test patterns for mocking external services like Supabase and Redis?

You can use standardized test patterns and mocking guidance for external services like Supabase, Redis, and OpenAI to ensure your integration tests and end-to-end tests pass the 80 percent coverage threshold.

What's the best way to implement a new authentication API using test-driven development?

The best way to implement a new authentication API using test-driven development is writing failing integration tests for login and signup flows first, implementing the endpoint to pass all tests, then verifying coverage meets the threshold before merging.