project-remove
Skill0 starsChanged 4 months agoMITView on GitHub
Remove a registered project from the setup. Use with /project-remove.
- Deletes or force-pushes
In this repository42 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- content-rewriteSkill
- content-writeSkill
- core-auditSkill
- core-bootstrapSkill
- core-commitSkill
- core-explainSkill
- core-finalizeSkill
- core-orchestrateSkill
- core-pullSkill
- core-setupSkill
- core-updateSkill
- design-convertSkill
- design-shipSkill
- design-tokensSkill
- dev-inspectSkill
- dev-learnSkill
- dev-manualSkill
- dev-optimizeSkill
- dev-securitySkill
- dev-shipSkill
- dev-tweakSkill
- game-debugSkill
- game-optimizeSkill
- game-shipSkill
- game-tweakSkill
- marketing-contentSkill
- marketing-researchSkill
- marketing-screenshotsSkill
- project-addSkill
- project-appSkill
- project-memorySkill
- project-planSkill
- project-researchSkill
- project-seedSkill
- project-syncSkill
- project-todoSkill
- project-tunnelSkill
- team-issuesSkill
- team-outsourceSkill
- team-reviewSkill
- team-verifySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 50
NEVER remove claude-config itself
- Distinctive: line 117
Only removes projects with link-based setup
- Distinctive: line 118
Always asks for confirmation
- Very specific: line 131
If project accidentally removed: git clone + /project-add
- Very specific: line 132
If links accidentally removed: recreate with ln -s (macOS) or mklink /J (Windows)
- Distinctive: line 133
If master config corrupted: restore from backup/git
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Project Remove
Removes a project with safe link removal (target stays intact).
Trigger
/project-remove [name] or /project-remove
Process
PHASE 1: Project Selection
If no name given:
- Scan
{projects_root}for projects with .claude/ links - Show list via AskUserQuestion
question: "Which project do you want to remove?"
header: "Project"
options:
- label: "[project-name-1]"
description: "{projects_root}/[project-name-1]"
- label: "[project-name-2]"
description: "{projects_root}/[project-name-2]"
# ... dynamically generated
multiSelect: falsePHASE 2: Validation
Check that project exists:
test -d "{projects_root}/[name]"
test -f "{projects_root}/[name]/.claude/settings.local.json"Safety checks:
- NEVER remove claude-config itself
- Warn if uncommitted changes
cd "{projects_root}/[name]" && git status --porcelainPHASE 3: Confirmation
question: "Are you sure you want to remove [name]?"
header: "Confirm"
options:
- label: "Yes, remove project"
description: "Removes project folder. Master config stays intact."
- label: "No, cancel"
description: "No changes"
multiSelect: falsePHASE 4: Project Folder Removal
Question:
question: "Do you want to remove the project folder?"
header: "Folder"
options:
- label: "Yes, remove everything (Recommended)"
description: "Removes {projects_root}/[name] completely"
- label: "No, keep folder"
description: "Only links removed, rest stays intact"
multiSelect: falseIf yes:
rm -rf "{projects_root}/[name]"PHASE 6: Wrap Up
Output:
Project [name] removed
- Project folder: [removed/kept]
- Master config: intactConfiguration
| Placeholder | macOS default | Windows default | Env var |
{projects_root} | $HOME/projects | C:\Projects | CLAUDE_PROJECTS_ROOT |
Resolution order (first match wins):
- Environment variable
.claude/paths.local.yaml(local per project, not in git)skills/project-add/paths.yaml(canonical defaults)
Restrictions
- Can NEVER remove claude-config (hard check)
- Only removes projects with link-based setup
- Always asks for confirmation
- Link removal is always safe (target intact)
Safety Notes
WHY unlink/rmdir and not rm -rf on links:
unlink(macOS) andrmdir(Windows) remove only the link pointerrm -rfordel /sfollows the link and removes TARGET files- This would destroy the master config!
Recovery:
- If project accidentally removed:
git clone+/project-add - If links accidentally removed: recreate with
ln -s(macOS) ormklink /J(Windows) - If master config corrupted: restore from backup/git
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
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.

