tdd

Enforce a red-green-refactor workflow for software feature implementation and bug resolution.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/rotnov/pycc --skill tdd-rotnov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/rotnov/pycc/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/rotnov/pycc --skill tdd-rotnov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of maintaining high code quality and reliability by enforcing a disciplined test-first development cycle, preventing regressions and ensuring features meet requirements before implementation.

Core Features & Use Cases

  • Red-Green-Refactor Cycle: Guides the developer through writing failing tests, implementing minimal code to pass, and cleaning up the implementation.
  • Integration Testing: Facilitates the creation of robust test suites that verify component interactions within the repository.
  • Use Case: When implementing a new feature or fixing a bug in the pycc compiler, use this skill to ensure that every change is validated by a corresponding test case before the code is merged.

Quick Start

Use the tdd skill to initiate a test-driven development cycle for the current feature implementation.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I implement a test-driven development workflow for new software features?

Test-driven development is enforced by guiding you through a strict red-green-refactor workflow, ensuring you write failing tests first, implement minimal code to pass, and then refactor to maintain software quality and prevent regressions.

Can I use test-driven development for both unit and integration testing scenarios?

Test-driven development workflows apply to both unit and integration testing scenarios within your repository, facilitating the creation of robust test suites that verify component interactions and ensure code correctness.

What's the best way to prevent regressions when fixing a bug in my codebase?

To prevent regressions during bug resolution, you should validate every change with a corresponding test case before merging code, adhering to a disciplined test-first development cycle that enforces code correctness.

Does this test-driven development approach require specific dependencies or framework setups?

The test-driven development workflow operates without external dependencies, requiring only adherence to the canonical workflow defined in your project-specific skill documentation to facilitate feature implementation and bug resolution.

Why should I use a red-green-refactor cycle instead of writing tests after implementation?

The red-green-refactor cycle ensures features meet requirements before implementation by maintaining high code quality and reliability, preventing regressions through a disciplined test-first development cycle rather than testing after the fact.