rename-plugin

To safely rename a plugin, this Skill validates the existing plugin directory, renames it to a kebab-case format, and updates metadata across marketplace files. It modifies plugin.json, marketplace.json, and README catalogs, then reports all changed files for your review without committing.

Renaming a marketplace plugin requires updating the plugin directory path, the plugin.json metadata file, the .claude-plugin/marketplace.json entries, and README catalog rows. This Skill automates these discovery and update steps to prevent manual errors during refactoring.

Yes, you can automatically refactor install paths and catalog entries by running the rename command with the current and new kebab-case names. The workflow updates directory paths, adjusts metadata, greps for remaining references, and bumps the plugin version to reflect the changes.

No, the rename workflow does not commit changes automatically. It operates safely by producing a list of modified files and warning on ambiguous matches, allowing you to review the updated directories and metadata before finalizing the repository changes.

When renaming a plugin directory, the Skill warns on ambiguous matches to ensure safe operation. It performs a repository-wide grep for remaining references after updating the primary metadata, helping you catch and resolve any unclear matches before committing.

Renaming a plugin requires bumping the version in plugin.json to reflect the installation path changes. This automated patch version increment ensures that the marketplace correctly registers the updated directory structure and metadata.