SkillAgentSearch skills...

rename-process

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.

Install / Use

npx skills add davidondrej/skills --skill rename-process

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Universal

Our assessment of rename-process

rename-process scores 82/100 on our quality scale, 3323rd of 4,698 Development & Engineering skills we index.

Its SKILL.md is 3.5 KB long, split into 5 sections and no code examples: a solid amount of guidance for an agent.

With 4,079 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so rename-process is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

rename-process compared with similar skills

All 4 of these similar skills score higher than rename-process; compare them before choosing.

SkillScoreStarsUpdatedFormat
rename-process (this skill)by davidondrej824.1k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md

Frequently asked questions

How do I install rename-process?
Run npx skills add davidondrej/skills --skill rename-process. The install tabs above show the steps for each supported agent.
Which AI agents does rename-process work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is rename-process safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is rename-process still maintained?
The repository was last updated about 2 months ago, so rename-process is actively maintained.

name: rename-process description: 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.

Execute

  1. Confirm the map. Record old/new names, exact real paths, Git remotes, repository identities/visibility, and affected machines. Inspect existing destinations, local changes, aliases, worktrees, services, and tool references. Resolve only missing scope; do not restart an already-approved naming discussion.
  2. Prepare once. Choose the supported update route before moving anything. Save private inventories and suitable backups. Pause affected writers and file copies; release processes that hold the old root. Stage required service/configuration edits and check their originals have not changed. If BB is affected, read BB path migration.
  3. Move and update together. Rename the real directory in place on the same filesystem. Never overwrite an independent destination or replace the existing private checkout with a fresh clone. Update remotes, tool references, necessary aliases, and service/configuration paths. Repair linked worktrees with git worktree repair; preserve missing registrations rather than pruning them.
  4. Verify affected use. Compare work, refs, stashes, ignored state, and worktree links. Check the actual tool/service workflow at the new path, not just file existence or a running process. Distinguish pre-existing failures from new ones. Once relevant checks pass, finish; broaden testing only for unresolved failures.
  5. Close out. Update current operational notes, resume paused work, and commit/push only within the authorized scope. Report completion, final paths/repository URLs, and any real remaining blocker. Separate completed changes from prepared ones.

Reusing the old name

For an approved split, fix and verify every old remote, alias, and dependent path before creating the new repository or checkout under that name. Check canonical repository identities: an old GitHub URL can redirect to the renamed repository. Verify the new repository's visibility and allowed contents independently; never copy private history into a fresh core repository.

If a check fails

Keep existing data intact and repair the specific broken reference. If rollback is needed, restore folders, configurations, and tool references together, then recheck access. Do not turn the rename into unrelated repair work.

Related Skills

View on GitHub
GitHub Stars4.1k
CategoryDevelopment
Updated1mo ago
Forks601

Languages

Shell

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions