name

Refactor generic variable names by running Sublime's anti-attractor procedure to propose justified renames. The procedure scans identifiers, evaluates naming patterns, and outputs a table of old to new mappings with a one-line justification for each change, applying updates only after explicit confirmation.

Fix inconsistent naming conventions by scanning identifiers for divergent name variants across local and exported boundaries. The anti-attractor procedure evaluates these patterns and proposes explicit old to new mapping tables with justifications to enforce consistent terminology across the project.

Yes, you can rename Manager, Helper, and Service suffix proliferation during code review. The Skill identifies these suffix patterns, evaluates them using the anti-attractor procedure, and proposes justified renames in an auditable table without applying any silent changes.

The anti-attractor procedure handles safe renames by following a disciplined four-step process to evaluate naming slop. It never renames silently, instead generating a table of proposed old to new identifier mappings with a justification for each concept, awaiting user confirmation before applying changes.

Yes, this refactoring approach applies to both local and exported function names. The anti-attractor procedure specifically targets divergent name variants across local and exported boundaries, ensuring consistent terminology and reducing cognitive load throughout the entire codebase.

You should avoid using automated rename proposals when you need silent, immediate changes without audit. This approach never renames silently; it requires explicit user confirmation and outputs a table of old to new mappings with justifications, making it unsuitable for rapid, unreviewed bulk modifications.