fix-bug
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
Security Assessment
About fix-bug
The 'fix-bug' skill is designed to guide users through the process of fixing bugs within the ClaudeBar system, utilizing Chicago School TDD (Test-Driven Development) along with root cause analysis and rich domain design. This skill addresses the need for systematically identifying, testing, and fixing bugs or unexpected behaviors in the software. It ensures that all bug fixes are tested and verified through a structured methodology, which minimizes the introduction of new issues while maintaining the integrity of the system.
FAQ
How should I use this skill when I encounter a bug?
You can use this skill when a bug is reported, when fixing defects in existing functionality, or when correcting behavior that violates the user's expectations. The workflow involves reproducing and understanding the bug, writing a failing test, and then fixing and verifying the issue.
Does this skill follow any particular development methodology?
Yes, this skill follows the Chicago School TDD methodology, which focuses on state-based testing, testing observable outcomes, and using mocks to stub dependencies.
What is the role of the 'Root cause' analysis?
The root cause analysis helps to understand why the bug is occurring in the first place, focusing on the underlying issues in the codebase or architecture. This analysis is essential before proceeding with the bug fix.
Install fix-bug
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
tddworks/ClaudeBar