bug-fixlisted

# Skill: bug-fix Fix a defect in the smallest, most root-causing way. The discipline is universal: reproduce before fixing, write the failing test first, falsify rival hypotheses before asserting a cause, identify root vs symptom, close the coverage gap that let it through, minimum diff, commit body documents why. ## Output rendering Code change — Show edits as a fenced ```diff block with +/− lines. Never describe the change in prose or a table. Table — When presenting several items that share the same fields, render a Markdown table. Cap at ~5 columns; beyond that, switch to a per-item detail list. Right-align numeric columns. ## When to invoke Even a one-line fix benefits from walking this discipline; it forces the question "is this fixing the cause or hiding it?" For multi-file changes that go beyond fixing one defect — refactors, new features triggered by discovering the bug — stop and use `new-spec` instead. This skill is for bug fixes, not opportunistic restructuring. ## Procedure ### Production emergency When users, security, or data are actively at risk, containment may precede the normal sequence below. Before any production mutation, confirm the exact action, intended scope, and blast radius with the user or operator unless that exact action was already approved in the current turn. Act only within existing operational authority and label the action **mitigation**. Preserve the minimum logs, traces, inputs, and timing evidence needed without extending the h