Quick Fix

Quick Fix is the bulk of a security-review checklist turned into a tool: the changes reviewers ask for on every script, applied consistently, with an audit trail in the code itself (each transform marks its work and version in a comment). Because nothing applies without an explicit preview and click, it’s safe to put in front of any operator.

Edit > Quick Fix (or right-click) dry-runs all five transforms against the caret’s enclosing function; strict mode considers the whole file. The list shows each fix as applicable or refused with a plain-English reason — “This script explicitly turns strict mode off; that looks deliberate, so this won’t override it” — and refusals that can be overridden carry a do-it-anyway row. Preview shows before and after; Apply splices only the enclosing function’s span; Cancel leaves the buffer byte-identical. Transforms are AST-based (ModuleWorkshop.Transforms), and dry-runs execute on a dedicated background runspace, so analysis never touches session state.

For a hands-on walkthrough, see the harden a script tutorial.

Think of Quick Fix as a careful colleague reading your function. It can wrap risky commands so failures are handled, add safety settings, and check your parameters. It shows you exactly what it wants to change, old version on the left, new on the right, and does nothing until you click Apply. When it declines to change something, it tells you why in a sentence.

Every applied transform is self-documenting in the modified code (marker comment with tool and version), so hardening changes remain attributable in review and diff history.