refactor-rename-for-clarity

Renaming variables and functions for clarity involves identifying ambiguous or misleading identifiers and replacing them with descriptive names that reveal intent. This skill systematically updates all declarations and usages across your codebase while preserving semantics, applying principles like intent-revealing names, searchability, and matching abstraction levels.

Effective refactoring naming follows three core principles: reveal intent through descriptive names, ensure identifiers are searchable, and match the abstraction level of the code context. Pattern-based renaming converts unclear conventions—like data to specificName, temp to previousValue, and flag to isEnabled—into consistent, maintainable names.

Yes. This skill applies systematic renaming to variables, functions, classes, and files across different languages during refactoring. It handles consistency audits where names are unclear or inconsistent, updating all usages simultaneously to maintain code semantics and prevent breakage.

Provide a list of ambiguous or misleading identifiers you want to clarify. The skill generates a rename plan with recommended target names based on naming principles, then applies the changes across all declarations and usages to refresh code readability.

Renaming is most effective after refactoring sessions when you audit code for clarity, or during consistency audits where naming conventions drift. Use it when variable, function, or class names obscure their purpose, mislead readers, or make code harder to search and maintain.