/remove-custom
Remove the active custom module repository and all its installed artifacts (skills, MCP servers, command overrides, scripts) from claude-code-setup.
$ npx -y skills add b33eep/claude-code-setup --agent claude-codeShips with claude-code-setup. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/remove-custom
Context preview
What this command does when you run it.
Remove the active custom module repository and all its installed artifacts (skills, MCP servers, command overrides, scripts) from claude-code-setup.
Command definition
remove-custom.mdRemove Custom Modules
Remove the active custom module repository and all its installed artifacts (skills, MCP servers, command overrides, scripts) from claude-code-setup.
Zero residue: deletes the git clone at `~/.claude/custom/`, every installed copy, and every tracking entry; restores base versions for commands that overrode a base command.
Only one custom repo can be active at a time, so no URL argument is needed.
Usage
/remove-custom
Tasks
1. **Check installation state**
- If `~/.claude/installed.json` doesn't exist → output the "no installation"
message and stop.
- If `installed.json` has no `custom_url` AND `~/.claude/custom/` doesn't
exist → output the "nothing to remove" message and stop.
2. **Execute removal** (1 Bash call)
Clone the latest claude-code-setup, run `--remove-custom`, then clean up:
temp=$(mktemp -d /tmp/claude-setup-XXXXXX) && \
git clone --depth 1 https://github.com/b33eep/claude-code-setup.git "$temp" 2>/dev/null && \
cd "$temp" && ./install.sh --remove-custom ; rm -rf "$temp"
The script handles:
- Removing every `custom:` skill from `~/.claude/skills/` and `installed.json`
- Removing every `custom:` MCP server from `~/.claude.json` and `installed.json`
- Deleting every custom command override; restoring base versions when a
base command exists in the claude-code-setup repo
- Deleting every custom script from `~/.claude/scripts/`
- Deleting `~/.claude/custom/` (the git clone)
- Clearing `custom_url` and `custom_version` from `installed.json`
- Rebuilding `~/.claude/CLAUDE.md`
3. **Report**
- Relay the counts printed by `install.sh`.
- If MCP servers were removed, remind the user to restart Claude Code.
Output
Success:
Removed custom repo: <url>
- N skill(s)
- M MCP server(s)
- K command(s) (base versions restored where available)
- L script(s)
- ~/.claude/custom/
- custom_url, custom_version
CLAUDE.md rebuilt.
IMPORTANT: Restart Claude Code to deactivate removed MCP servers.
Nothing to remove:
No custom repo registered (~/.claude/installed.json has no custom_url, and
~/.claude/custom/ does not exist). Nothing to remove.
No installation:
claude-code-setup is not installed. Nothing to remove.
Network error (clone failed):
Unable to reach GitHub.
Manual removal:
cd /path/to/claude-code-setup
./install.sh --remove-custom
Read more
Remove Custom Modules
Remove the active custom module repository and all its installed artifacts (skills, MCP servers, command overrides, scripts) from claude-code-setup.
Zero residue: deletes the git clone at `~/.claude/custom/`, every installed copy, and every tracking entry; restores base versions for commands that overrode a base command.
Only one custom repo can be active at a time, so no URL argument is needed.
Usage
/remove-custom
Tasks
1. **Check installation state**
- If `~/.claude/installed.json` doesn't exist → output the "no installation"
message and stop.
- If `installed.json` has no `custom_url` AND `~/.claude/custom/` doesn't
exist → output the "nothing to remove" message and stop.
2. **Execute removal** (1 Bash call)
Clone the latest claude-code-setup, run `--remove-custom`, then clean up:
temp=$(mktemp -d /tmp/claude-setup-XXXXXX) && \ git clone --depth 1 https://github.com/b33eep/claude-code-setup.git "$temp" 2>/dev/null && \ cd "$temp" && ./install.sh --remove-custom ; rm -rf "$temp"
The script handles:
- Removing every `custom:` skill from `~/.claude/skills/` and `installed.json`
- Removing every `custom:` MCP server from `~/.claude.json` and `installed.json`
- Deleting every custom command override; restoring base versions when a
base command exists in the claude-code-setup repo
- Deleting every custom script from `~/.claude/scripts/`
- Deleting `~/.claude/custom/` (the git clone)
- Clearing `custom_url` and `custom_version` from `installed.json`
- Rebuilding `~/.claude/CLAUDE.md`
3. **Report**
- Relay the counts printed by `install.sh`.
- If MCP servers were removed, remind the user to restart Claude Code.
Output
Success:
Removed custom repo: <url> - N skill(s) - M MCP server(s) - K command(s) (base versions restored where available) - L script(s) - ~/.claude/custom/ - custom_url, custom_version CLAUDE.md rebuilt. IMPORTANT: Restart Claude Code to deactivate removed MCP servers.
Nothing to remove:
No custom repo registered (~/.claude/installed.json has no custom_url, and ~/.claude/custom/ does not exist). Nothing to remove.
No installation:
claude-code-setup is not installed. Nothing to remove.
Network error (clone failed):
Unable to reach GitHub. Manual removal: cd /path/to/claude-code-setup ./install.sh --remove-custom
Persistent memory for Claude Code via Markdown files. 📖 Read the Documentation for detailed guides, tutorials, and reference.
Repo: b33eep/claude-code-setup
Other commands on claude-code-setup.
- /add-custom
Add a custom module repository (company or personal) to claude-code-setup.
Open command - /catchup
After `/clear` or new chat, understand recent changes.
Open command - /claude-code-setup
Manage your claude-code-setup installation: check status, upgrade, install, and remove modules.
Open command - /delegate
Spawn a teammate to work on a separate task independently. You continue your own work and get notified when the teammate finishes.
Open command - /design
A structured way to plan complex features before implementing. Works through: Problem → Options → Solution → Stories → Finalize.
Open command - /do-review
Trigger a code review on your recent changes using the comprehensive-review plugin. This is Step 3 in the Development Flow — review before committing.
Open command

