uninit-workoslisted

Reverse what /init-workos did, removing only the scaffold files it created and leaving every other document and folder untouched. Use whenever the user says 'uninit workos,' 'undo init-workos,' 'remove the workos scaffold,' 'tear down workos,' 'reset this back,' 'revert init-workos,' or asks to clean up the CLAUDE.md / MEMORY.md / ARCHIVE.md scaffolding without losing their existing content. Identifies scaffold files by a sentinel marker (`workos-init-scaffold v1`) that init-workos writes at the top of every file it creates. Files without the sentinel — including any document the user wrote — are never deleted or modified. When a scaffold file has been edited since init, shows the user what changed and asks before removing.
dylanmoo/workos-plugin · ★ 0 · Data & Documents · score 70

Install: claude install-skill dylanmoo/workos-plugin

# Uninit WorkOS The reverse of `/init-workos`. Walks the workspace, removes only the scaffold files that `/init-workos` created, and leaves every other file and folder untouched. ## What this skill does Three things, and only three things: 1. **Finds** every scaffold file by grepping for the sentinel `workos-init-scaffold v1` that `/init-workos` writes at the top of each file it creates. 2. **Classifies** each scaffold file as clean (unchanged from the original template) or edited (the user added content after init). 3. **Removes** clean scaffold files automatically; asks the user file-by-file what to do with edited ones. Anything without the sentinel — pre-existing documents, files the user wrote later, files created by `/create-project` — is never touched. ## The sentinel `/init-workos` writes this exact line at the top of every file it creates (after YAML frontmatter when present): ```html  ``` This skill matches the substring `workos-init-scaffold v1`. Anything containing that token is a scaffold file. Anything not containing it is user content and stays. If the user removed the sentinel manually, the file looks like user content to this skill — it will be left alone. That's intentional: when in doubt, preserve. ## Step 1: Confirm the workspace root Use the current working directory as the workspace root. State the path back to the user and confirm before scanni