Structured Bugfix Workflow FAQs

Question 1

What is the core rule of the Bugfix skill?

Accepted Answer

The core rule is to never apply a fix without first creating a failing test that reproduces the bug, ensuring the fix is verified and prevents future regressions.

Question 2

How does the reproduction phase work?

Accepted Answer

The skill attempts to replicate the reported issue in the local environment and documents the specific steps, expected results, and actual results before proceeding to the planning phase.

Question 3

Does this skill require user intervention?

Accepted Answer

Yes, the workflow requires user approval on the fix plan (Phase B2) before moving to implementation to ensure the proposed solution aligns with the project's requirements.

Question 4

Can I use this skill for general code refactoring?

Accepted Answer

No, this skill specifically enforces minimal changes to fix bugs; refactoring or 'improving' surrounding code is considered an anti-pattern within this workflow and should be handled separately.

Question 5

What happens if the root cause of a bug is unclear?

Accepted Answer

The workflow includes a debugging pattern where temporary, structured debug logging is added to trace execution paths and test hypotheses before any implementation changes are made.

Structured Bugfix Workflow

主要功能

使用场景

Structured Bugfix Workflow

主要功能

使用场景