Plan stack-wide rebranding migrations across code, docs, and assets.
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-rebrand
Please help me install this Agent Skill. Skill: rcode-rebrand Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/core/rcode-rebrand Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-rebrand
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.
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.
High-intent search queries and answers about installing and using this skill.
Repository rebranding migration requires a full inventory of old-brand references, surface-by-surface categorization, and phased commit decomposition with compatibility windows. This approach splits the brittle big-bang change into controlled, reviewable steps.
During a project rename, inventory package identity, repository metadata, environment variables, assets, copy, redirects, documentation, code references, social handles, and legal materials. Group these references by rebrand surface to plan safe, isolated commits.
Maintain environment variable compatibility during a package rename by keeping old and new names working together throughout a transition window. This protects public-facing references and links from breaking production workflows during the migration.
Decompose a codebase rename by applying one rebrand surface per commit. This phased commit decomposition ensures changes remain isolated, reviewable, and reversible, with verification required after each surface modification.
Yes, a phased migration approach applies to renaming company assets, copy, social handles, and legal materials. It requires categorizing each external channel as a distinct surface to ensure compatibility windows and verification steps are applied.
Big-bang project name changes break documentation and redirects because one name change affects multiple surfaces simultaneously without compatibility windows. Splitting the migration into surface-by-surface phases with verification prevents missing hidden dependencies.
magnus919Generate a markdown-based Brand Identity package with strategy, visual identity, voice, governance, and asset inventory.
CANTAGESTUDIOPlan Git commit strategies for codebase refactorings with branch naming and commit granularity.
timequityConfigure URL schemes, Universal Links, and App Links for iOS and Android deep linking.
devmuslimSelect and design release rollout strategies based on risk and user base.
