repo-rename

Topics in the source

• Repo Rename
• Scope
• Workflow
• Completion

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. Preview the complete GitHub, Git, filesystem, and agent-continuity mutation set before applying a repository rename. 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

This is an excerpt. Refer to the complete source and its current requirements.