agentleFS
PaulRBergPaulRBerg/agent-skills/skills/repo-rename/SKILL.md

repo-rename

Skill104 starsChanged 3 days agoMITView on GitHub

If a slash or dollar invocation already added these instructions to the conversation, follow them directly. In that case, do not invoke this skill again through a skill tool. Review the helper's complete GitHub, Git, filesystem, and agent-continuity mutation set before applying a repository rename. Keep user-facing previews and completion reports to affected surfaces and aggregate file and occurrence counts. Do not list replacement paths or per-file counts unless the user explicitly requests them. - Rename the current GitHub repository,…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a slash or dollar invocation already added these instructions to the conversation, follow them directly.

    line 12
  2. Distinctive:

    Do not list replacement paths or per-file counts unless the user explicitly requests them.

    line 17
  3. Very specific:

    If the repository has no Git remotes, rename only local state: the folder, continuity references, and repository content.

    line 24
  4. Very specific:

    Only when the repository has an active Claude Code or Codex transcript, update literal old paths in ~/.claude/projects, ~/claude/projects …

    line 27
  5. Distinctive:

    Update absolute repository paths, exact name fields, whole-line repository names or headings, and GitHub URLs for the repository.

    line 30
  6. Distinctive:

    Do not modify other transcript stores, archives, remotes, or repositories.

    line 40
  7. Distinctive:

    If neither exists, state that the transcript-continuity update does not apply.

    line 50
  8. Very specific:

    If --dry-run was requested, summarize the preview as described below and stop.

    line 72
  9. Very specific:

    Verify the helper's result with gh repo view, git remote get-url origin, pwd -P, and a search for remaining old absolute-path/name …

    line 95
  10. Distinctive:

    If a moved Python environment retains old paths, reinstall its locked packages with the project's existing package manager.

    line 98

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Repo Rename

If a slash or dollar invocation already added these instructions to the conversation, follow them directly. In that case, do not invoke this skill again through a skill tool.

Review the helper's complete GitHub, Git, filesystem, and agent-continuity mutation set before applying a repository rename. Keep user-facing previews and completion reports to affected surfaces and aggregate file and occurrence counts. Do not list replacement paths or per-file counts unless the user explicitly requests them.

Scope

  • Rename the current GitHub repository, matching local folder, and origin URL.
  • With two path arguments, move the source repository to the destination without changing its name, GitHub identity, or origin. Both paths must have the same folder name. Preview missing parent directories before creating them.
  • If the repository has no Git remotes, rename only local state: the folder, continuity references, and repository content. The helper then skips the GitHub rename and the origin update. A repository with any remote still requires a valid GitHub context.
  • Only when the repository has an active Claude Code or Codex transcript, update literal old paths in ~/.claude/projects, ~/claude/projects when present, ~/.codex/sessions, and ~/.codex/config.toml. This continuity update does not apply to repos with no active transcripts.
  • Update absolute repository paths, exact name fields, whole-line repository names or headings, and GitHub URLs for the repository. Preserve other old-name occurrences, including imports, prose, and command selectors. Exclude VCS, dependencies (including Python virtual environments), caches, and generated build directories.
  • For a same-name move, replace only the old absolute repository path inside repository files.
  • By default, use tracked repository files and skip PROMPT.md, TODO.md, and symlinks before reading replacement candidates. Prune excluded directories during discovery. When the user explicitly authorizes updating notes, dependencies, caches, or generated files, pass --include-local-state to both preview and apply. This includes those repository text files while preserving file permissions. Symlinks, binary files, and .git remain excluded.
  • The helper honors CLAUDE_CONFIG_DIR and CODEX_HOME, gates continuity updates on active transcripts, and replaces only the absolute repository path in continuity stores and Codex config.
  • Do not modify other transcript stores, archives, remotes, or repositories.

Workflow

  1. Resolve the source repository from the first of two path arguments, or from the current directory for a rename. Check whether it has any active AI chat transcript before treating continuity preservation as in scope:
    • Claude Code: resolve ${CLAUDE_CONFIG_DIR:-~/.claude}/projects/<encoded-repo-path> (the absolute repo path with every non-alphanumeric character replaced by -) and check it exists and is non-empty.
    • Codex: resolve ${CODEX_HOME:-~/.codex}/sessions and check whether any session file references the exact absolute repo path.
    • If neither exists, state that the transcript-continuity update does not apply. In that case, the rename may still proceed for the GitHub, git, filesystem, and repository-content changes below.
  2. Resolve the skill directory and run the helper from the repository to produce a read-only preview:

    uv run <skill-dir>/scripts/repo-rename.py <new-name> --dry-run

    For a same-name move, run from any directory:

    uv run <skill-dir>/scripts/repo-rename.py <source-path> <destination-path> --dry-run

    The helper requires a clean worktree, matching GitHub repo/folder names, a free target path, and valid GitHub context. For a repository with no remotes, it requires only a clean worktree and a free target path. It reports "local_only": true and a local:<old>-><new> confirmation token. It prints the old/new repo and paths, exact confirmation token, external commands, directory moves, every replacement file, occurrence counts, and rollback coverage. Same-name moves use move:<absolute-source>-><absolute-destination> tokens. Linked worktrees and external Git directories are unsupported.

  3. If --dry-run was requested, summarize the preview as described below and stop. A successful dry run must not change the GitHub repo, remote, folder, config, transcripts, or repository files.
  4. Present a compact preview, then continue in the same turn unless --dry-run was requested. Treat the rename request as authorization for the planned mutations. Do not require a separate confirmation message. For a local-only preview, state that no GitHub or origin change occurs. Lead with ### 🔎 Rename preview — no changes made. Summarize GitHub, source and destination folders, origin, aggregate replacement counts, and rollback coverage. Use short prose or a compact table. If any preview fact changes, regenerate the preview and continue within the requested scope.

    For same-name moves, show the unchanged GitHub identity and origin, and state whether parent directories need creation.

  5. Pass the preview's exact token to the helper internally:

    uv run <skill-dir>/scripts/repo-rename.py <new-name> --apply --confirm '<owner/old->owner/new>'

    For a same-name move, pass both paths and the preview's move: token instead.

    The helper re-runs preflight, backs up every replacement file, applies deterministic literal replacements, and attempts rollback on failure. Never bypass its clean-tree, target-path, or token checks.

  6. Verify the helper's result with gh repo view, git remote get-url origin, pwd -P, and a search for remaining old absolute-path/name references in the listed scope. Report intentional remaining matches separately.

    If a moved Python environment retains old paths, reinstall its locked packages with the project's existing package manager. Then rerun the repository's test command.

Completion

Dry-run completion is a summarized mutation preview with zero writes. Apply completion requires the new GitHub identity, folder, remote, and affected continuity references to agree, plus a clean verification report. If rollback is incomplete, stop and lead with ### ⛔ Rollback incomplete, then report every failed rollback action before doing anything else. On success, use ### ✅ Repository renamed and a surface/expected/verified table. Keep helper JSON, confirmation tokens, commands, paths, URLs, and rollback errors exact and undecorated.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.