rename-discipline

To prevent cosmetic renames from cluttering pull request diffs, enforce a rename discipline that requires every identifier or file name change to carry specific functional justification or address a technical conflict. This ensures only substantive changes appear in code reviews.

Enforcing naming conventions during refactoring requires applying project-level naming guides to identifier modifications. A rename discipline mechanism evaluates whether a change provides informational value or resolves a scope conflict, reverting personal preference edits that lack clear functional justification.

Code reviewers revert gratuitous renames by flagging unnecessary identifier changes during the pull request feedback loop. A standardized protocol then guides the development agent to revert the cosmetic changes, maintaining diff clarity and separating substantive logic from stylistic preferences.

File name changes in a pull request are warranted when they provide specific informational value or resolve a technical scope conflict. Changes driven by personal preference or stylistic updates without functional justification should be rejected to maintain diff quality.

Automated refactoring workflows support reverting unnecessary identifier changes by applying rename discipline rules. When a builder or fixer agent attempts a cosmetic rename, the skill identifies it as gratuitous and guides the agent to revert the change before the diff is finalized.

Gratuitous renames negatively impact code review quality by forcing reviewers to waste time disentangling substantive logic changes from stylistic ones. Enforcing rename discipline prevents this clutter, ensuring pull request diffs contain only justified, functional modifications.