Rename Process
Coordinate project or repository renames and moves involving Git, BB, services, or...
Install
npx skills add davidondrej/skills --skill rename-process -g -a claude-code -y- Repository
- davidondrej/skills4.2k
- Category
- Git and review
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 828 tokens
- Runs scripts
- No, instructions only
What it does
Coordinate project or repository renames and moves involving Git, BB, services, or multiple machines. Preserve work and history while updating operational paths. Excludes ordinary file, code-symbol, and thread-title renames.
Rename process
Finish the requested rename with the smallest verified set of changes. Use one coordinator working outside the directory being renamed. Keep existing approvals; ask only for missing decisions or authorization.
Keep the scope small
- Touch only systems affected by the changed name or path. Keep unrelated Git pulls/rebases, cleanup, dependency updates, document reconciliation, and implementation separate.
- Preserve the existing repository, local work, ignored files, credentials, stashes, worktrees, and conversation identities. A repository split requires explicit scope for the new repository and its visibility/content.
- Keep product branding, domains, runtime/plugin identities, and historical documents unchanged unless their change is requested or necessary. Avoid bulk replacement of every old-name occurrence.
- Use current supported commands. Do not build a general migration framework, launch extra agents, or require a shutdown/database migration without a concrete need.
