skills.rest
kiminmonaco
kiminmonacoCOMMUNITY
Explore all skills by this author →
GitHub

fix-bug

Reproduce bugs, write failing tests, and apply minimal fixes for ClaudeBar.

7|2|Updated Sep 28, 2022
Search Tags:#tdd#debugging#domain-driven-design#quality-assurance#bug-fix#software-testing
One-click install
npx skills add https://github.com/kiminmonaco/ClaudeBar --skill fix-bug-kiminmonaco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-bug
Source: https://github.com/kiminmonaco/ClaudeBar/tree/main/.claude/skills/fix-bug
Command: npx skills add https://github.com/kiminmonaco/ClaudeBar --skill fix-bug-kiminmonaco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides developers through a disciplined, end-to-end bug-fix workflow for ClaudeBar using Chicago School TDD and rich domain design, helping teams reproduce issues, write failing tests, implement minimal fixes, and verify correctness.

Core Features & Use Cases

  • Reproduce and understand bugs with structured steps and root-cause analysis.
  • Write failing tests (red) to expose defects and validate correct behavior.
  • Implement minimal fixes focused on restoring domain invariants and passing tests.
  • Verify fixes by running targeted tests and full test suites to prevent regressions.

Quick Start

Provide a repeatable sequence: reproduce the issue, add a failing test, apply a minimal fix, and re-run tests.

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?▼

To fix a bug using Chicago School TDD, you reproduce the issue, write a failing test to expose the defect, apply a minimal fix to pass the test, and run the full suite to prevent regressions.

What is the best way to reproduce a bug for root-cause analysis?▼

The best way to reproduce a bug for root-cause analysis is to follow a structured workflow that identifies the defect, exposes it with a failing test, and verifies the domain invariants before applying a minimal fix.

How does test-driven development preserve domain invariants during a bug fix?▼

Test-driven development preserves domain invariants by requiring a failing test that exposes the defect, ensuring the minimal fix restores correct behavior and passes both targeted and full test suites.

When should I use TDD for software testing and bug fixes?▼

You should use TDD for software testing and bug fixes when you have a reproducible bug report, need root-cause analysis, or want to ensure a safe minimal fix that prevents feature regressions.

Can I use domain-driven design to prevent feature regressions?▼

Yes, you can use domain-driven design to prevent feature regressions by applying minimal changes that restore domain invariants, then verifying correctness by running targeted tests and the full test suite.

Why does my bug fix keep breaking other tests?▼

Your bug fix might break other tests if it lacks regression verification; applying minimal changes guided by a failing test and running the full test suite ensures domain invariants are preserved without introducing new defects.

Related Skills

Explore More Software Engineering Skills→
jMertajMerta
130

bug-triage

Convert ambiguous bug reports into reproducible repros, root-cause explanations, and minimal fixes.

Community
Advanced
cdalsoniiicdalsoniii

Domain Invariant Assertion

Analyze Go source and test files to verify domain invariants.

Community
Advanced
thomasslobodathomassloboda

typescript-ddd-development

Generate TypeScript domain code following Domain-Driven Design principles.

Community
Intermediate
DavidSchmidt00DavidSchmidt00
2

test-driven-development

Guide developers through the Red-Green-Refactor cycle for TDD.

Community
Advanced