rcode-rebrand

What problem does it solve?

Rebranding is risky because one name change can affect packages, repositories, environment variables, assets, copy, URLs, social handles, documentation, code references, and legal materials all at once. This Skill turns that brittle big-bang change into a controlled migration with clear checkpoints.

Core Features & Use Cases

• Inventory all brand surfaces: Find and classify every old-brand reference across the repository.
• Decompose safely: Split the migration into one surface per commit so changes are reviewable and reversible.
• Protect compatibility: Keep old and new names working together during a transition window for env vars, links, and public-facing references.
• Use case: Rename a product, company, or package across code, docs, assets, and external channels without missing hidden dependencies or breaking production workflows.

Quick Start

Ask the assistant to scan the repository for every old-brand reference, group the results by rebrand surface, and produce a phased commit plan with compatibility notes and communication steps.