skills.rest
suriyel
suriyelCOMMUNITY
Explore all skills by this author →
GitHub

long-task-tdd

Enforce the Test-Driven Development Red-Green-Refactor cycle with failing tests before implementation.

178|43|Updated Feb 12, 2026
Search Tags:#code quality#testing#tdd#refactoring#software development#test-driven development
One-click install
npx skills add https://github.com/suriyel/longtaskforagent --skill long-task-tdd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: long-task-tdd
Source: https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-tdd
Command: npx skills add https://github.com/suriyel/longtaskforagent --skill long-task-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces the Test-Driven Development (TDD) Red-Green-Refactor cycle, ensuring that code is written only after failing tests are created and that tests are comprehensive.

Core Features & Use Cases

  • Strict TDD Enforcement: Guarantees that no implementation code is written without a preceding failing test.
  • Comprehensive Test Rules: Enforces rules for test category coverage, negative test ratio, assertion quality, and the necessity of real integration tests.
  • Use Case: When developing a new feature, this Skill ensures you write unit and integration tests first, verify they fail, then write the minimal code to pass, and finally refactor, leading to more reliable and maintainable software.

Quick Start

Follow the Red-Green-Refactor cycle to implement the current feature.

Frequently Asked Questions about long-task-tdd

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

FAQPage Schema
How do I enforce the test-driven development cycle when writing implementation code?▼

To enforce test-driven development, this Skill mandates the Red-Green-Refactor cycle, ensuring all implementation code is preceded by failing tests. It blocks code generation until comprehensive tests for happy paths and edge cases are verified.

What is the minimum negative test ratio required for comprehensive test coverage?▼

The minimum negative test ratio is enforced by this Skill alongside strict assertion quality rules. It mandates covering error handling and edge cases to ensure your test suite is comprehensive and robust against failures.

How do I handle external dependencies when writing integration tests?▼

When writing integration tests for external dependencies, this Skill mandates including real integration tests rather than mocks. This validates actual interactions and ensures your software handles external system behaviors correctly.

Can I use this TDD approach for features requiring strict UI testing protocols?▼

Yes, this TDD approach adheres to strict UI testing protocols when applicable. It ensures that user interface components are validated through the same Red-Green-Refactor cycle, maintaining high code quality for UI features.

Why does my refactoring step fail when test coverage is incomplete?▼

Your refactoring step fails because this Skill strictly enforces test category coverage before allowing code refactoring. It requires a minimum negative test ratio and high-quality assertions to guarantee safe and maintainable code improvements.

What's the best way to start a new feature using strict test-driven development?▼

The best way to start a new feature using strict test-driven development is to follow the Red-Green-Refactor cycle. Write failing unit and integration tests first, then write the minimal code to pass, and finally refactor.

Related Skills

Explore More Software Engineering Skills→
tneztnez

bootstrap

Initialize the .docent directory structure and configuration for new projects.

Community
Basic
GainInsightDevGainInsightDev

af-analyse-test-coverage

Analyze test coverage reports to identify untested code paths and gaps.

Official
Intermediate
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
lexlerlexler
225

bdd-with-approvals

Organize behavior definitions as executable domain-language fixtures with approval-based verification.

Community
Intermediate