skills.rest
jtvaris
jtvarisCOMMUNITY
Explore all skills by this author →
GitHub

tdd-bug-fix

Reproduce bugs with a failing test, then implement a minimal fix.

Updated Mar 15, 2026
Search Tags:#testing#tdd#debugging#regression#red-green-refactor#bug-fix
One-click install
npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill tdd-bug-fix-jtvaris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-bug-fix
Source: https://github.com/jtvaris/sunday-night-dynasty/tree/main/.agents/skills/testing/tdd-bug-fix
Command: npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill tdd-bug-fix-jtvaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fix bugs using red-green-refactor — reproduce the bug as a failing test first, then fix it. Use when fixing bugs to ensure they never regress.

Core Features & Use Cases

  • Reproduce bugs by writing a failing test (RED) to capture the bug
  • Implement a minimal fix that satisfies the test (GREEN)
  • Verify against the full test suite to prevent regressions

Quick Start

Reproduce the bug with a failing test, then implement the minimal fix and validate the full test suite.

Frequently Asked Questions about tdd-bug-fix

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

FAQPage Schema
How do I fix a bug using red-green-refactor?▼

To fix a bug using red-green-refactor, you first write a failing test that reproduces the bug, then implement a minimal fix that passes the test and prevents future regressions.

What is the best way to reproduce a bug with a failing test before fixing it?▼

The best way to reproduce a bug is to write a failing test that captures the exact conditions of the bug. This validates the issue exists before you apply any code changes to fix it.

How do I prevent regression when debugging and applying code fixes?▼

You prevent regression during debugging by requiring a failing test that reproduces the bug and validating that your minimal fix passes the entire test suite before deployment.

When should I use test-driven development for bug fixing?▼

You should use test-driven development for bug fixing when you need to ensure bugs never regress, requiring a failing test to capture the bug and a verifiable fix to validate the suite.

What are the limitations of writing a failing test to reproduce a bug?▼

A limitation of writing a failing test to reproduce a bug is that it requires an existing test suite to validate the fix. If the bug is not easily isolated, writing a precise failing test can be difficult.

Related Skills

Explore More Software Engineering Skills→
bjornjeebjornjee
19

fix

Reproduce a software defect in an isolated git worktree, then validate a minimal fix with tests.

Community
Advanced
bennybennisonbennybennison

debugging-methodology

Diagnose software bugs through reproduction, isolation, hypothesis testing, and regression verification.

Community
Intermediate
pko89403pko89403
1

test

Automate test-driven development workflows for bug reproduction, failing test creation, and fix verification.

Community
Basic
hamzaPixlhamzaPixl
2

investigate

Diagnose software failures through evidence-driven root-cause debugging workflows.

Community
Advanced