cluster-rename

Rename chunk directories and update frontmatter references with dry-run previews.

3|1|Updated Jan 8, 2026

Search Tags:#automation #refactoring #codebase #rename #frontmatter #chunks #prefix

Ready to run

npx skills add https://github.com/netguy204/vibe-engineer --skill cluster-rename

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cluster-rename
Source: https://github.com/netguy204/vibe-engineer/tree/main/.agents/skills/cluster-rename
Command: npx skills add https://github.com/netguy204/vibe-engineer --skill cluster-rename

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Renaming chunk prefixes is error-prone when frontmatter references and directory names must stay in sync; this Skill automates the safe, auditable rename of chunk namespaces.

Core Features & Use Cases

Rename chunk directories matching an old prefix to a new prefix.
Update frontmatter fields (created_after and related references) to reflect the new prefix.
Perform a dry-run to preview changes and avoid collisions before applying them.

Quick Start

Run ve chunk cluster-rename <old_prefix> <new_prefix> to rename chunk prefixes and update references.

Frequently Asked Questions about cluster-rename

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

FAQPage Schema

How do I safely rename chunk directory prefixes and update frontmatter references?▼

To rename chunk prefixes safely, this Skill automates directory renaming and synchronizes all relevant frontmatter references, including created_after and related fields, to reflect the new prefix.

What is the best way to automate codebase refactoring for chunk namespaces?▼

Automating codebase refactoring for chunk namespaces is best handled by applying automated directory renaming and frontmatter synchronization, ensuring all chunk prefix changes stay in sync without manual errors.

Can I preview directory renaming changes before applying them to my codebase?▼

Yes, you can preview directory renaming changes by performing a dry-run, which detects potential collisions and shows exactly how frontmatter references will be updated before any modifications are applied.

Does the chunk rename process support multi-prefix rename scenarios?▼

The chunk rename process supports both single-prefix and multi-prefix rename scenarios, handling projects organized by chunk namespaces while maintaining frontmatter synchronization across all affected directories.

Are rename operations auditable and ready for rollback?▼

Rename operations are auditable and rollback ready, implementing post-rename verification and safety checks like collision detection to ensure all frontmatter references and directory changes are tracked and recoverable.