TDD Skill

Enforce project-specific TDD rules and coverage thresholds across application layers.

1|Updated Mar 21, 2026

Search Tags:#testing #tdd #quality assurance #ci/cd #software development #code coverage

Ready to run

npx skills add https://github.com/cmbays/mokumo --skill tdd-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: TDD Skill
Source: https://github.com/cmbays/mokumo/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/cmbays/mokumo --skill tdd-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces project-specific rules and best practices for Test-Driven Development (TDD) on top of a general TDD methodology, ensuring consistent code quality and test coverage.

Core Features & Use Cases

Layered Test Coverage: Defines specific unit and integration test coverage thresholds for different layers of the application (e.g., domain logic, repositories, API routes).
Mandatory Coverage Targets: Identifies critical files that require 100% test coverage.
Pipeline Integration: Outlines the role of TDD in different stages of the CI/CD pipeline (Plan, Build, Review).
Use Case: Ensure that all financial calculations in src/domain/lib/money.ts are covered by unit tests before any code changes are merged.

Quick Start

Invoke the TDD skill to ensure all critical financial functions meet 100% test coverage.

Frequently Asked Questions about TDD Skill

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

FAQPage Schema

How do I enforce TDD rules and coverage thresholds across different application layers?▼

You enforce TDD rules by defining specific unit and integration test coverage thresholds for different application layers like domain logic and API routes. This ensures consistent code quality and adherence to the Red-Green-Refactor methodology across your software development pipeline.

What is the best way to ensure 100% test coverage for critical financial calculations?▼

The best way to ensure 100% test coverage for critical financial calculations is to mandate coverage targets for essential files. This approach identifies critical modules and prevents code changes from merging until full test coverage verification is complete.

How does Test-Driven Development integrate into CI/CD pipeline stages?▼

Test-Driven Development integrates into CI/CD pipeline stages by outlining specific roles during the Plan, Build, and Review phases. This enforces continuous adherence to test coverage thresholds and the Red-Green-Refactor methodology throughout the software development lifecycle.

Can I apply custom test layer maps for domain logic and repositories in my software development pipeline?▼

Yes, you can apply custom test layer maps to define specific unit and integration test coverage thresholds for domain logic and repositories. This enforces project-specific TDD rules and ensures critical modules meet mandatory coverage requirements before merging.

Why do I need defined verification commands for coverage checks?▼

You need defined verification commands for coverage checks to validate that critical files meet mandatory 100% test coverage thresholds. This enforces TDD best practices and prevents untested code changes from advancing through the software development pipeline.