patch-or-fix

A patch masks failure symptoms without addressing the underlying issue, while a root-cause fix resolves the actual defect. Diagnosing this distinction requires evidence gathering and structured stepwise reasoning to ensure durable software quality and prevent recurring bugs.

Perform root-cause analysis by systematically gathering evidence, diagnosing whether the change addresses the underlying defect or merely patches symptoms, and documenting structured fixes with clear justification to guide the code review process.

Document a bug fix verdict by producing a reproducible output that classifies the change as a patch or root-cause fix, includes the diagnostic rationale, and provides concrete code changes to copy directly into PR notes for faster approvals.

Yes, providing a bug fix scenario generates concrete, implementable fixes with real code changes and clear justification. The output is designed to be deployable rather than just offering diagnostic observations or theoretical recommendations.

Use a structured diagnosis workflow when evaluating pull requests or design reviews to ensure changes do not merely mask failures. It enforces explicit root-cause analysis across the development lifecycle to maintain durable software quality.