skills.rest
DigiStrique-Solutions
DigiStrique-SolutionsOFFICIAL
Explore all skills by this author →
GitHub

tdd

Enforce RED-GREEN-REFACTOR cycles with 80%+ test coverage before code changes.

1|Updated Apr 2, 2026
Search Tags:#testing#tdd#refactoring#red-green-refactor#code-quality#software-development
One-click install
npx skills add https://github.com/DigiStrique-Solutions/sentinel --skill tdd-digistrique-solutions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/DigiStrique-Solutions/sentinel/tree/main/skills/tdd
Command: npx skills add https://github.com/DigiStrique-Solutions/sentinel --skill tdd-digistrique-solutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-Driven Development workflow enforcement helps teams ensure tests are written before implementation, maintain high coverage, and avoid anti-patterns during feature development, bug fixes, and refactors.

Core Features & Use Cases

  • Enforces RED-GREEN-REFACTOR cycle with 80%+ coverage and edge-case handling
  • Requires writing a failing test before implementing code
  • Guides safe refactoring and anti-pattern avoidance during API or component changes

Quick Start

Describe a new feature, begin by writing a failing test that reproduces the desired behavior, implement the minimal solution to make the test pass, then refactor while keeping all tests green.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I enforce a strict RED-GREEN-REFACTOR cycle during software development?▼

To enforce a strict RED-GREEN-REFACTOR cycle, this Skill mandates writing a failing test before any implementation, ensuring the minimal solution passes, and then guiding safe refactoring. It actively imposes this workflow for new features, bug fixes, and API changes.

How does Test-Driven Development handle fixing existing bugs?▼

For fixing bugs, Test-Driven Development requires you to first write a failing test that reproduces the specific bug. Once the failing test confirms the issue, you implement the minimal code fix to make it pass, ensuring the bug is permanently resolved.

What is the minimum test coverage required when writing tests before implementation?▼

The minimum test coverage required before completing code changes is 80 percent or higher. The workflow enforces this coverage threshold while also providing guidance on edge-case handling and anti-pattern avoidance during the development process.

Can I use this TDD workflow for refactoring existing code and introducing new APIs?▼

Yes, you can use this TDD workflow for refactoring existing code and introducing new APIs. It applies the mandatory RED-GREEN-REFACTOR cycle to these scenarios, guiding safe refactoring and preventing anti-patterns while keeping all tests green.

What are the limitations of enforcing a mandatory failing test before implementation?▼

A limitation of enforcing a mandatory failing test before implementation is that it requires strict adherence to the RED-GREEN-REFACTOR sequence, which may slow down rapid prototyping. It mandates 80%+ coverage and imposes rigid workflow constraints across all code changes.

Related Skills

Explore More Software Engineering Skills→
caobingshengcaobingsheng
1

tdd-workflows-tdd-red

Generate failing tests to define expected behavior in the TDD red phase.

Community
Advanced
Cor-IncorporatedCor-Incorporated
4

tdd-workflow

Guide the RED-GREEN-REFACTOR cycle for TDD with 80%+ test coverage.

Official
Intermediate
janewilkinjanewilkin

test

Run pytest test suites and generate code coverage reports.

Community
Intermediate
TheBushidoCollectiveTheBushidoCollective
187

bdd-principles

Conduct Three Amigos sessions and produce executable scenarios for BDD workflows.

Official
Intermediate