address-all-similar-instances-skill

To fix all similar bug instances, you need to generalize the single defect into a broader failure class, perform a discovery sweep, and apply clustered remediation to related surfaces. This ensures you resolve sibling UI states and client-server parity issues.

Bug generalization is the process of identifying the underlying user-facing problem pattern from a single proven defect rather than stopping at literal duplicates. You need it during codebase refactoring to prevent incomplete fixes across the same component family.

To ensure UI state consistency when fixing a bug, you must inspect the nearest hierarchy including sibling UI states and client-server instrumentation twins. This adjacency-first discovery approach catches workflow-adjacent lookalikes.

The best way to sweep a codebase for related defect instances is to use programmatic search for a first-pass discovery, build an adjacency map of exact duplicates and same-class siblings, then apply clustered remediation with verification testing.

Fixing one bug instance leaves similar workflow failures behind because the broader failure class remains unaddressed. Without an adjacency map to identify same-class siblings and workflow-adjacent lookalikes, clustered remediation is never applied to the nearest related surfaces.

Yes, you can generalize a single defect and fix client-server parity issues across the same workflow by inspecting client/server instrumentation twins during the discovery sweep and applying clustered remediation with completion testing.