rename

Rename specification plan directories and update internal references in documentation.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/cloudvoyant/claudevoyant --skill rename-cloudvoyant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rename
Source: https://github.com/cloudvoyant/claudevoyant/tree/main/plugins/spec/skills/rename
Command: npx skills add https://github.com/cloudvoyant/claudevoyant --skill rename-cloudvoyant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the management of your project specifications by allowing you to easily rename plans and ensuring all internal references are automatically updated, preventing broken links and confusion.

Core Features & Use Cases

  • Safe Renaming: Renames plan directories and updates README.md to reflect the new name.
  • Reference Updates: Automatically corrects self-references within plan.md files.
  • Conflict Resolution: Handles potential naming conflicts by suggesting alternatives.
  • Use Case: You've created a plan named feature-auth but later decide authentication-module is more descriptive. This Skill renames the directory and updates all mentions of feature-auth within your project's spec files.

Quick Start

Use the rename skill to change the plan named 'old-plan-name' to 'new-plan-name'.

Frequently Asked Questions about rename

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

FAQPage Schema
How do I rename a spec plan directory and update all references in my project documentation?

To rename a spec plan directory and update references, provide the old and new names. The tool renames the directory, updates the README.md, and corrects self-references inside plan.md files to ensure documentation consistency.

What is the best way to update internal documentation references when changing a plan name?

Updating internal documentation references during a plan name change is handled automatically by validating the new name for uniqueness and correcting self-references within plan.md files to prevent broken links and confusion.

How does renaming a specification plan directory affect my project's README and spec files?

Renaming a specification plan directory directly updates the project README.md to reflect the new name and automatically corrects internal self-references within the associated plan.md files to maintain structural consistency.

Does the rename process check for naming conflicts before changing a plan directory?

Yes, the rename process checks for naming conflicts by validating the new plan name for uniqueness before execution. It handles potential conflicts by suggesting alternatives and confirms the operation to ensure safe renaming.

What happens to broken links in plan.md files after renaming a spec directory?

Broken links in plan.md files are automatically corrected after renaming a spec directory. The tool ensures consistency across plan directories and README files by updating internal self-references to reflect the new name.

When should I use an automated tool to rename plan directories instead of manual updates?

You should use an automated tool to rename plan directories when you need to safely update multiple internal references across README files and plan.md documentation, preventing manual errors and broken links.