rename-plugin

Rename plugins across marketplace files and update catalog entries.

1|Updated Feb 26, 2026

Search Tags:#automation #documentation #plugin #refactor #marketplace #rename

Ready to run

npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill rename-plugin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rename-plugin
Source: https://github.com/mattbobambrose/mattbobambrose-claude-skills/tree/main/plugins/project-tools/skills/rename-plugin
Command: npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill rename-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Renaming a plugin in a marketplace requires coordinated updates to directories, metadata, and documentation and is error-prone when done manually; this Skill automates the discovery and update steps and reports changes for review.

Core Features & Use Cases

Atomic rename workflow: Validate the old plugin exists, verify the new name format, rename the plugin directory, and update plugin metadata.
Repository-wide updates: Edit plugin.json and marketplace.json entries, update README catalog rows and per-plugin sections, and grep for remaining references.
Safe operation: Warn on ambiguous matches, bump the plugin version (patch) to reflect installation changes, and produce a list of modified files for user review without committing changes.

Quick Start

Run the rename-plugin command with the current plugin name followed by the desired kebab-case new name to perform a repository-wide rename and receive a summary of changed files.

Frequently Asked Questions about rename-plugin

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

FAQPage Schema

How do I safely rename a plugin in a Claude marketplace repository?▼

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.

What files need to be updated when renaming a marketplace plugin?▼

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.

Can I automatically refactor plugin install paths and catalog entries during a rename?▼

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.

Does the rename workflow commit changes to the repository automatically?▼

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.

What happens if there are ambiguous matches when renaming a plugin directory?▼

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.

Why does renaming a plugin require bumping the version in plugin.json?▼

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.