skills.rest
notque
notqueCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Guide RED-GREEN-REFACTOR TDD cycles across Go, Python, and JavaScript projects.

415|44|Updated Mar 18, 2026
Search Tags:#workflow#testing#tdd#python#javascript#go#best-practices
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill test-driven-development-notque
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/test-driven-development
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill test-driven-development-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill guides developers through a disciplined test-driven development cycle (RED-GREEN-REFACTOR), ensuring tests drive implementation, fail for the right reasons, and maintain green test suites during refactors.

Core Features & Use Cases

  • Enforces RED-GREEN-REFACTOR cycles across languages and projects
  • Validates test failures, guides minimal implementation, and supports safe refactoring
  • Provides comprehensive guidance and examples for Go, Python, and JavaScript workflows

Quick Start

Start by writing a failing test, run it to confirm the right failure, then implement the minimal code to pass and refactor while keeping the tests green

Frequently Asked Questions about test-driven-development

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

FAQPage Schema
How do I enforce a strict RED-GREEN-REFACTOR cycle in my code?▼

A strict RED-GREEN-REFACTOR cycle requires writing a failing test first, validating the failure reason, implementing minimal code to pass it, and refactoring while keeping the test suite green.

How do I start test-driven development for bug fixes and feature development?▼

Start test-driven development for bug fixes or features by writing a failing test that captures the desired behavior, confirming the failure, then writing the minimal implementation needed to turn it green before refactoring.

Does this TDD workflow support Python, JavaScript, and Go projects?▼

Yes, this TDD workflow applies directly to Python, JavaScript, and Go projects, providing comprehensive language-specific guidance and examples for validating failures and guiding minimal implementation across these environments.

What is the best way to prevent over-engineering when writing tests?▼

The best way to prevent over-engineering during TDD is to implement only what is explicitly tested, ensuring every code change is driven by a failing test and avoiding speculative abstractions during the REFACTOR phase.

Why do I need to validate test failures before writing implementation code?▼

Validating test failures before writing implementation code ensures the test fails for the right reasons, guaranteeing that your subsequent minimal code changes actually drive the expected behavior and the test suite turns green reliably.

Related Skills

Explore More Software Engineering Skills→
markus41markus41
18

Claude Code Testing Workflows

Guides software testing across TDD, unit, integration and end-to-end for multiple languages.

Community
Intermediate
hidonguyenhidonguyen

ck:test

Execute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
alexfalkowskialexfalkowski
2

testing-standards

Enforce behavior-driven development and repository-defined test harnesses across unit, integration, and feature tests.

Community
Advanced