How do I install the Move Project skill?

Run npx skillmds@latest add anothersava/move-project in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Move Project skill do?

Move/Rename Project It is listed under Coding & Dev Tools on SkillMD.

Is Move Project safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Move Project?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Move Project free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Move Project?

AnotherSava (@anothersava) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Move Project by anothersava — Agent Skill

Name: Move Project
Author: AnotherSava

File contents

Move/Rename Project

Move or rename the current project folder while preserving all associated Claude Code data (session logs, memory, subagent history).

Process

Ask for the new location. If the user didn't provide one as an argument, ask:

Where should I move this project? Provide a new folder path (relative or absolute) or just a new name (keeps the same parent directory).
Resolve paths. Determine:
- OLD_PATH: the current working directory (absolute)
- NEW_PATH: the target — if the user gave just a name, resolve it relative to the parent of OLD_PATH
- Validate that NEW_PATH does not already exist
Compute Claude data directory names. Apply the path-mangling rule documented in ~/.claude/skills/skill/references/claude-project-memory-paths.md to both OLD_PATH and NEW_PATH to derive OLD_KEY and NEW_KEY. That file is the canonical reference for the mangling rule, the cross-platform CWD recipe, and common mistakes.

Preview and confirm. Show the user what will happen:

Project folder:  OLD_PATH → NEW_PATH
Claude data:     ~/.claude/projects/OLD_KEY → ~/.claude/projects/NEW_KEY

Ask: "Proceed? (y/n)"

Execute on confirmation. Run these commands (the user must run them outside this session since the working directory is about to move):

Print the commands for the user to copy and run:
```
mv "OLD_PATH" "NEW_PATH"
mv "$HOME/.claude/projects/OLD_KEY" "$HOME/.claude/projects/NEW_KEY"
```
Important: Claude Code must NOT be running from the project directory when the move happens. Tell the user to:
1. Exit this Claude session
2. Run the printed commands from any other directory
3. Open a new Claude session from the new location

Important

This skill does NOT execute the move itself — it prints the commands. Moving the working directory out from under a running session would break it.
On Windows, print both bash (mv) and PowerShell (Move-Item) variants so the user can run from either shell. On macOS / Linux, print only the bash mv form.
If ~/.claude/projects/OLD_KEY doesn't exist, skip that step (project may not have Claude data yet).

---name: move-projectdescription: Move/Rename Project---# Move/Rename ProjectMove or rename the current project folder while preserving all associated Claude Code data (session logs, memory, subagent history).## Process1. **Ask for the new location.** If the user didn't provide one as an argument, ask: > Where should I move this project? Provide a new folder path (relative or absolute) or just a new name (keeps the same parent directory).2. **Resolve paths.** Determine: - `OLD_PATH`: the current working directory (absolute) - `NEW_PATH`: the target — if the user gave just a name, resolve it relative to the parent of `OLD_PATH` - Validate that `NEW_PATH` does not already exist3. **Compute Claude data directory names.** Apply the path-mangling rule documented in `~/.claude/skills/skill/references/claude-project-memory-paths.md` to both `OLD_PATH` and `NEW_PATH` to derive `OLD_KEY` and `NEW_KEY`. That file is the canonical reference for the mangling rule, the cross-platform CWD recipe, and common mistakes.4. **Preview and confirm.** Show the user what will happen: ``` Project folder: OLD_PATH → NEW_PATH Claude data: ~/.claude/projects/OLD_KEY → ~/.claude/projects/NEW_KEY ``` Ask: "Proceed? (y/n)"5. **Execute on confirmation.** Run these commands (the user must run them outside this session since the working directory is about to move): Print the commands for the user to copy and run: ``` mv "OLD_PATH" "NEW_PATH" mv "$HOME/.claude/projects/OLD_KEY" "$HOME/.claude/projects/NEW_KEY" ``` **Important:** Claude Code must NOT be running from the project directory when the move happens. Tell the user to: 1. Exit this Claude session 2. Run the printed commands from any other directory 3. Open a new Claude session from the new location## Important- This skill does NOT execute the move itself — it prints the commands. Moving the working directory out from under a running session would break it.- On Windows, print both bash (`mv`) and PowerShell (`Move-Item`) variants so the user can run from either shell. On macOS / Linux, print only the bash `mv` form.- If `~/.claude/projects/OLD_KEY` doesn't exist, skip that step (project may not have Claude data yet).

Frequently asked questions

Move Project