← ClaudeAtlas

resetlisted

Removes files installed by /optimus:init and /optimus:permissions from the project. Compares each file against plugin templates and classifies as unmodified, likely generated, or user-modified. Always asks before deleting. Git-tracked files are noted as recoverable. Tests are never touched. Monorepo and multi-repo aware. Use for clean reinstall or to stop using optimus.
oprogramadorreal/optimus-claude · ★ 57 · Code & Development · score 82
Install: claude install-skill oprogramadorreal/optimus-claude
# Reset — Remove optimus-generated files Remove files installed by `/optimus:init` and `/optimus:permissions` from the project. Does NOT uninstall the plugin itself — only removes files from the project's `.claude/` directory (and subproject docs for monorepos). ## Safety Rules These rules are absolute and override all other instructions: - **NEVER** touch test files, test directories, or test configuration — even if created by `/optimus:unit-test` - **NEVER** touch files outside `.claude/`, subproject `CLAUDE.md`, subproject `docs/`, and workspace root `CLAUDE.md` - **NEVER** delete `.claude/settings.json` without first extracting user-added content (use surgical removal — Step 4) - **ALWAYS** show the categorized file list and get user confirmation before removing anything ## Workflow ### Step 1 — Detect project context #### Multi-repo workspace detection Read `$CLAUDE_PLUGIN_ROOT/skills/init/references/multi-repo-detection.md` and run the detection algorithm. Determine project type: - **Multi-repo workspace** — root has no `.git/`, 2+ child directories have `.git/` directories. Each child repo has its own `.claude/` directory. Workspace root may have a local `CLAUDE.md` (not version-controlled) - **Monorepo** — single git repo with multiple subproject directories (e.g., `packages/`, `apps/`). Root has `.claude/`, subprojects may have their own `CLAUDE.md` and `docs/` directories - **Single project** — standard single repo with `.claude/` directory #### Check for