rename-discipline

Regulate identifier and file renames to keep pull request diffs substantive.

3|2|Updated May 12, 2026

Search Tags:#code review #pull request #refactoring #naming convention #diff quality

Ready to run

npx skills add https://github.com/kriscendobot/garden --skill rename-discipline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rename-discipline
Source: https://github.com/kriscendobot/garden/tree/main/skills/rename-discipline
Command: npx skills add https://github.com/kriscendobot/garden --skill rename-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the cluttering of pull requests with cosmetic or gratuitous renames that force reviewers to waste time disentangling substantive changes from stylistic ones.

Core Features & Use Cases

Justification Enforcement: Ensures every rename carries specific informational value or addresses a technical conflict.
Reviewer Feedback Loop: Provides a standardized protocol for reverting unnecessary renames when flagged by maintainers.
Use Case: When a developer attempts to rename a test-local variable for personal preference, this Skill identifies it as gratuitous and guides the agent to revert the change to maintain diff clarity.

Quick Start

Apply the rename-discipline skill to review the current pull request diff and revert any identifiers that do not meet the criteria for a warranted rename.

Frequently Asked Questions about rename-discipline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent cosmetic code renames from cluttering my pull request diffs?▼

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.

What is the best way to enforce naming conventions during a refactoring workflow?▼

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.

How do code reviewers revert gratuitous variable renames in a PR?▼

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.

When should I allow file name changes in a pull request?▼

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.

Does automated refactoring support reverting unnecessary identifier changes?▼

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.

Why do gratuitous renames negatively impact code review quality?▼

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.