fix-bug

To fix a bug without masking symptoms, you must first reproduce the failure, trace the root cause in the owning subcomponent, apply a minimal patch, and verify the reproduction passes. This prevents speculative edits from causing regressions.

The best way to reproduce a regression is to turn the user's bug report into a concrete failing test case. This ensures your debugging workflow targets the actual failure path before you attempt any root cause analysis or patching.

Perform root cause analysis for runtime failures by locating the owning subcomponent that produces the wrong output. Apply the smallest code change necessary to prevent the failure, ensuring you avoid symptom-masking edits.

Yes, minimal patching aids regression testing by limiting changes to the smallest fix that prevents wrong output. After patching, re-run the reproduction case and check adjacent instances to verify the broken behavior is resolved.

Update documentation during a bug fix workflow only when user-visible behavior changes. This constraint ensures your root-cause patches and minimal changes do not introduce unnecessary documentation overhead for internal regressions.

Reproduction is required before diagnosing incorrect outputs because it confirms the failure path. Without a concrete failing case, root cause tracing becomes speculative and risks applying symptom-masking edits instead of a true bug fix.