skills.rest
dushyantkhosla
dushyantkhoslaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sp-test-driven-development

Implement Test-Driven Development with the Red-Green-Refactor cycle.

1|Updated May 2, 2026
Search Tags:#code quality#TDD#test-driven development#software testing#development process
One-click install
npx skills add https://github.com/dushyantkhosla/agent-skills --skill sp-test-driven-development-dushyantkhosla
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sp-test-driven-development
Source: https://github.com/dushyantkhosla/agent-skills/tree/main/skills/sp-test-driven-development
Command: npx skills add https://github.com/dushyantkhosla/agent-skills --skill sp-test-driven-development-dushyantkhosla

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of implementing new features or bug fixes without adequate testing, leading to potential bugs and quality issues in the codebase.

Core Features & Use Cases

  • Test-Driven Development Process: Encourages writing tests before implementation to ensure functionality and quality.
  • Red-Green-Refactor Cycle: A structured approach to developing software, iterating through writing a failing test, making it pass, and then refactoring.
  • Guidance on Best Practices: Provides insights on when to apply TDD, understanding the TDD cycle, and common anti-patterns to avoid.

Quick Start

Start by writing a failing test for the new feature or bugfix you're working on. Observe the test fail, then write the minimum code to make it pass.

Frequently Asked Questions about sp-test-driven-development

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

FAQPage Schema
What is the Red-Green-Refactor cycle in test-driven development?▼

The Red-Green-Refactor cycle is a test-driven development process where you write a failing test, implement the minimum code to make it pass, and then refactor the code for quality and reliability.

How do I write tests before code to improve software quality?▼

To improve software quality, start by writing a failing test for a new feature or bugfix, observe the failure, then write the minimum implementation code required to make the test pass successfully.

When should I apply test-driven development practices?▼

You should apply test-driven development practices when implementing new features or bug fixes to prevent potential bugs and ensure codebase quality, especially aiming for a disciplined software development approach.

What are common test-driven development anti-patterns to avoid?▼

Common test-driven development anti-patterns include writing tests after implementation and skipping the refactoring step, which this Skill guides you to avoid through structured best practices and process discipline.

Does test-driven development work for fixing bugs in an existing codebase?▼

Yes, test-driven development works for bug fixes by starting with a failing test that reproduces the bug, then writing the minimum code to make the test pass and ensure the issue is resolved reliably.

Related Skills

Explore More Software Engineering Skills→
streamlitstreamlit
224

setting-up-streamlit-environment

Set up Python virtual environments with dependency specifications for Streamlit apps.

Official
Intermediate
santanapolsantanapol

test-driven-development

Enforce a test-first workflow using Red-Green-Refactor and Prove-It Pattern.

Community
Advanced
tarekBassiounytarekBassiouny

Najaah LMS - Code Quality Agent

Enforces code quality standards for the Najaah LMS project using Pest, PHPStan, and Laravel Pint.

Community
Advanced
adolfoaranaes12adolfoaranaes12
2

refactor-code

Refactor code incrementally with test-driven validation and automatic rollback.

Community
Advanced