Why does this skill require a bd issue for every bug?

Creating a bd issue ensures that every defect is tracked from discovery to closure, providing a documented history, clear reproduction steps, and a link to the final resolution.

How does this skill help find the root cause of a bug?

It integrates with the 'debugging-with-tools' skill, using internet research and codebase investigation to look beyond immediate symptoms and identify the underlying logic error.

Can I skip the regression test for small fixes?

No. A core rule of this skill is that every bug must have a failing test (RED phase) before a fix is implemented to prove the bug exists and ensure it never returns.

Is this workflow suitable for production emergencies?

Yes. While hotfixes can be abbreviated, the skill requires that you still create the bd issue and add regression tests immediately afterward to maintain system integrity.

Systematic Bug Fixing

Name: Systematic Bug Fixing
Author: withzombies

bywithzombies

•

Security & Testing

Standardizes the end-to-end bug resolution process from discovery and tracking to regression testing and verification.

About

The Systematic Bug Fixing skill implements a rigorous, TDD-based workflow for handling software defects within Claude Code. It ensures every bug is tracked via a 'bd' issue, investigated for root causes rather than symptoms, and validated with a failing regression test before a fix is applied. By enforcing a strict sequence—track, debug, test-driven fix, and verification—this skill prevents regressions and ensures high-quality, documented resolutions for both development and production issues.

Key Features

Systematic verification against the full test suite before closure
Mandatory TDD workflow with failing regression tests (RED phase)
13 GitHub stars
Root cause investigation using specialized debugging tools
Integrated 'bd' issue tracking for bug lifecycle management
Automated documentation and git-linked issue resolution

Use Cases

Resolving unexpected behaviors during development with full audit trails
Fixing reported user bugs with permanent regression prevention
Systematically investigating complex production issues to find root causes

About

Key Features

Systematic verification against the full test suite before closure
Mandatory TDD workflow with failing regression tests (RED phase)
13 GitHub stars
Root cause investigation using specialized debugging tools
Integrated 'bd' issue tracking for bug lifecycle management
Automated documentation and git-linked issue resolution

Use Cases

Resolving unexpected behaviors during development with full audit trails
Fixing reported user bugs with permanent regression prevention
Systematically investigating complex production issues to find root causes