everywhere-elselisted

# Everywhere Else ## The failure mode this fixes A bug gets found in one scenario, one endpoint, one template — and fixed *there*. The report says "fixed," the test goes green, everyone moves on. But the codebase has nineteen siblings built by the same hand, from the same copy-paste, with the same defect — and the fix just made instance #7 correct while #1–6 and #8–20 still lie. The user discovers this one sibling at a time, each discovery costing a full debugging session that ends in "oh, it's the same bug again." Agents are biased toward the point fix: the task said "fix the chart in scenario 12," so scenario 12 gets fixed and the task is "done." Nobody asked the question that turns a point fix into a real fix: **is this defect a member of a population?** ## When to Use This Skill - You just fixed a defect in one instance of anything that has siblings — handlers, templates, scenarios, components, parsers, fixtures, migrations, configs - The fix corrected a *pattern* (wrong field semantics, missing null check, stale API shape) rather than a one-off typo - The codebase contains parallel surfaces that must stay consistent (every page that renders X, every job that emits Y) - A report is about to say "fixed" and the diff touches one file in a directory of twenty look-alikes - The user asks "did you do that anywhere else?" — if they have to ask, the skill fired too late **Don't use when:** the defect is genuinely unique to its site (a typo in one string), or the "siblings"