agentleFS
AirMileAirMile/claude-config/skills/project-remove/SKILL.md

project-remove

Skill0 starsChanged 4 months agoMITView on GitHub

Remove a registered project from the setup. Use with /project-remove.

  • Deletes or force-pushes

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
  1. Very specific:

    NEVER remove claude-config itself

    line 50
  2. Distinctive:

    Only removes projects with link-based setup

    line 117
  3. Distinctive:

    Always asks for confirmation

    line 118
  4. Very specific:

    If project accidentally removed: git clone + /project-add

    line 131
  5. Very specific:

    If links accidentally removed: recreate with ln -s (macOS) or mklink /J (Windows)

    line 132
  6. Distinctive:

    If master config corrupted: restore from backup/git

    line 133

≈ “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.

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

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:

  1. Scan {projects_root} for projects with .claude/ links
  2. 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: false

PHASE 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 --porcelain

PHASE 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: false

PHASE 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: false

If yes:

rm -rf "{projects_root}/[name]"

PHASE 6: Wrap Up

Output:

Project [name] removed

- Project folder: [removed/kept]
- Master config: intact

Configuration

PlaceholdermacOS defaultWindows defaultEnv var
{projects_root}$HOME/projectsC:\ProjectsCLAUDE_PROJECTS_ROOT

Resolution order (first match wins):

  1. Environment variable
  2. .claude/paths.local.yaml (local per project, not in git)
  3. 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) and rmdir (Windows) remove only the link pointer
  • rm -rf or del /s follows 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) or mklink /J (Windows)
  • If master config corrupted: restore from backup/git

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.