New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Rename Process

by davidondrej in davidondrej/skills

Coordinate project or repository renames and moves involving Git, BB, services, or multiple machines.

MITAuto-check passedDevelopment

Install Rename Process

skills CLI
$ npx skills add davidondrej/skills --skill rename-process -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davidondrej/skills rename-process --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davidondrej/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ops-and-setup/rename-process .claude/skills/rename-process && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rename-process
GitHub stars
4.1k
Token cost
~896 tokens
SKILL.md length
451 words
Files
3 (incl. references)
Skills in repo
51
Repo updated
First seen
Licence
MIT

At a glance

Coordinate project or repository renames and moves involving Git, BB, services, or multiple machines.

  • Works in 5 steps: Confirm the map. Record old/new names,… → Prepare once. Choose the supported… → Move and update together. Rename the… → …
  • Development work in your project
  • SKILL.md covers Keep the scope small, Execute, Reusing the old name and If a check fails
  • Calls git

What it does

Rename Process is an agent skill from davidondrej/skills. 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.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/bb-cutover.md`).

It sits in Development. It works with Git. The repository describes itself as: access to david ondrej's personal agent skills. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/rename-process”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the map. Record old/new names, exact real paths, Git remotes, repository identities/visibility, and affected machines. Inspect…
  2. Prepare once. Choose the supported update route before moving anything. Save private inventories and suitable backups. Pause affected…
  3. Move and update together. Rename the real directory in place on the same filesystem. Never overwrite an independent destination or replace…
  4. Verify affected use. Compare work, refs, stashes, ignored state, and worktree links. Check the actual tool/service workflow at the new…
  5. Close out. Update current operational notes, resume paused work, and commit/push only within the authorized scope. Report completion…

What it can do on your machine

Read from SKILL.md and the folder at commit 7874889. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rename Process loads about 896 tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 451 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~896
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davidondrej/skills at commit 7874889, republished under its MIT licence (© davidondrej). 451 words, ~896 tokens.

Download SKILL.mdSave it as .claude/skills/rename-process/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
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.
Show full SKILL.md (97 more words)Show less

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.

© davidondrej, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/ops-and-setup/rename-process of davidondrej/skills.

  • SKILL.md
  • agents/openai.yaml
  • references/bb-cutover.md

Open the folder on GitHubat commit 7874889

Compare with similar skills

Rename Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rename Process compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rename Process this skilldavidondrej/skills4.1k—~896Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins11k9 repos~2.6kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Finishing A Development Branchfarm-fe/farm5.6k34 repos~1.8kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    11k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Finishing A Development Branch

    farm-fe/farm

    A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…

    5.6k GitHub starsUsed in 34 repos~1.8k tokens
    DevelopmentAuto-check passed

  • Migrate Internal Package into Ghost

    TryGhost/Ghost

    Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    56k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

More from davidondrej/skills

All 51 skills in this repo

  • Nagent

    davidondrej/skills

    Launch a new bb worker thread with the right project, model, worktree, and task brief.

    4.1k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check: notes

  • Browser Harness

    davidondrej/skills

    Direct browser control via CDP. An agent skill from davidondrej/skills.

    4.1k GitHub starsUsed in 2 repos~3k tokens
    Auto-check passed

  • Persistent Localhost

    davidondrej/skills

    Manage persistent dev servers, APIs, and other local processes on a port using macOS LaunchAgents.

    4.1k GitHub stars~618 tokensUpdated yesterday
    Auto-check passed

  • Reset Cursor Acp

    davidondrej/skills

    Reset a stuck Cursor ACP thread in <chat-system and reload its configuration.

    4.1k GitHub stars~728 tokensUpdated yesterday
    Auto-check passed

  • Anti Sleep

    davidondrej/skills

    Keep a Mac awake for a set duration or while a process runs.

    4.1k GitHub stars~640 tokensUpdated yesterday
    Auto-check: warnings

  • Bb CLI

    davidondrej/skills

    Use this when controlling bb. An agent skill from davidondrej/skills.

    4.1k GitHub stars~823 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Rename Process

What does Rename Process do?

Coordinate project or repository renames and moves involving Git, BB, services, or multiple machines. Rename Process is an agent skill from davidondrej/skills. Coordinate project or repository renames and moves involving Git, BB, services, or multiple machines.

When should I use Rename Process?

Rename Process fits situations like: development work in your project.

How do I install Rename Process in Claude Code?

Run `npx skills add davidondrej/skills --skill rename-process -a claude-code`. Or copy the skill folder (skills/ops-and-setup/rename-process in davidondrej/skills) into .claude/skills/rename-process in your project. Claude Code loads it when a task matches its description.

How do I install Rename Process in Codex?

Run `npx skills add davidondrej/skills --skill rename-process -a codex`. Or copy the skill folder (skills/ops-and-setup/rename-process in davidondrej/skills) into .agents/skills/rename-process in your project. Codex loads it when a task matches its description.

Can I use Rename Process in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davidondrej/skills --skill rename-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rename-process, .gemini/skills/rename-process, .github/skills/rename-process and .opencode/skills/rename-process in your project.

What does Rename Process need to run?

Going by SKILL.md and its folder, Rename Process needs the command-line tools its instructions call (git).

Does Rename Process access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Rename Process safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rename Process use?

Rename Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rename Process use?

About 896 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 907 tokens, read only when the agent opens those files.

What are the alternatives to Rename Process?

Skills that share tags, products or a category with Rename Process: Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Code Design Rationale Investigator (cursor/plugins, 11k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rename Process?

davidondrej (a GitHub user) maintains it in davidondrej/skills, which has 4,112 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 8, 2026.

Source: davidondrej/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.