fix-bug

Name: fix-bug
Availability: InStock
Author: tddworks

Reproduce, diagnose, and fix ClaudeBar bugs using Chicago School TDD.

1.4k|127|Updated Dec 20, 2025

Search Tags:#unit tests #tdd #reproduction #root-cause-analysis #test-driven-development #fix-bug #domain design

Ready to run

npx skills add https://github.com/tddworks/ClaudeBar --skill fix-bug-tddworks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-bug
Source: https://github.com/tddworks/ClaudeBar/tree/main/.claude/skills/fix-bug
Command: npx skills add https://github.com/tddworks/ClaudeBar --skill fix-bug-tddworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide for fixing bugs in ClaudeBar following Chicago School TDD and rich domain design. Use this skill when: (1) User reports a bug or unexpected behavior (2) Fixing a defect in existing functionality (3) User asks "fix this bug" or "this doesn't work correctly" (4) Correcting behavior that violates the user's mental model

Core Features & Use Cases

Chicago School TDD guided bug fixing workflow
Root cause analysis to identify the underlying issue
Domain-driven design to maintain invariants and ensure robust fixes
Phase-based approach: Reproduce & Understand, Write Failing Test, Fix & Verify

Quick Start

Follow the structured Chicago School TDD workflow to reproduce, diagnose, and verify bug fixes.

Frequently Asked Questions about fix-bug

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

FAQPage Schema

How do I fix a bug using Chicago School TDD?▼

Fix a bug using Chicago School TDD by first reproducing the defect, writing a failing test that captures the broken behavior, then applying a minimal, domain-first fix to resolve the root cause.

What is the best way to reproduce and verify a bug fix with TDD?▼

The best way to reproduce and verify a bug fix with TDD is to isolate the unexpected behavior in a failing unit test, correct the domain logic, and run full regression validation to ensure invariants are maintained.

How does root-cause analysis work in test-driven development?▼

Root-cause analysis in test-driven development involves identifying the underlying domain logic failure causing the defect, then writing a failing test that exposes that specific issue before applying a minimal fix.

Can I use this TDD bug fixing workflow for unexpected behavior in existing functionality?▼

Yes, you can use this workflow for unexpected behavior in existing functionality by reproducing the user-reported defect, writing a failing unit test, and correcting the logic while maintaining domain invariants.

Why does domain design matter when fixing bugs?▼

Domain design matters when fixing bugs because it ensures the fix maintains system invariants and addresses the root cause rather than patching symptoms, resulting in robust and regression-safe behavior.