以證據驅動的缺陷修復

---
name: bug-fixing
license: MIT
description: >-
  Reproduce failures, regressions, and data/UI inconsistencies; trace the real execution path to the root cause, make a minimal authorized repair, and verify related paths.
  Scale evidence collection, testing, and challenge to actual risk. Not for new-feature planning or test design alone.
---

# Evidence-Driven Bug Fixing

Find the first boundary on the actual failure path that violates the correct rule. Fix the entire defect class at the layer responsible for that rule, and demonstrate recovery with the original failing input and related paths. Reduce redundant process, not causal evidence or applicable checks.

Do not change product code when only diagnosis was requested. When repair is already authorized, continue within scope without asking again. For a new product decision, expanded scope, changed data/permission/security semantics, or an unauthorized external action, complete independent investigation and a concrete proposal first, then ask only for the missing decision. Check command side effects too. For a growing incident, existing authorization may permit reversible containment while preserving original evidence; containment is not a root-cause fix.

## Select Work for the Actual Situation