--- name: dayz-clean-workspace description: Remove DayZ scaffolds and their deployed artifacts. For each managed mod under workspace// (native /dayz-new-mod scaffold OR /dayz-import-mod link), removes the workspace folder/link, the P:\\ junction (only if it points at our workspace), and the P:\Mods\@\ deployed dir. For imported mods, the external source folder is NEVER touched - only the link is removed. Never touches mods you didn't scaffold (subscribed/installed mods at !Workshop are safe). --include-server also removes .server/ (refuses if legacy workspace/_server/ still exists; delete it manually first). Interactive confirmation by default; --yes skips it. --- > **Path note:** `` in commands below is the absolute path of this skill's folder. When the agent loads this skill the harness exposes the skill's base directory; substitute it before running. Sibling skills are reached via `\..\dayz-X\`. # /dayz-clean-workspace Reset the DayZ workspace by removing scaffolds and their deployed artifacts. Safe - only removes mods that match a `workspace//` entry (folder OR link containing `config.cpp` + `$PBOPREFIX$`). User-installed / subscribed mods under `\!Workshop\` are never touched. Handles both native scaffolds (`/dayz-new-mod`) and imported links (`/dayz-import-mod`): - **Native scaffold** - folder is removed recursively. - **Imported link** - the link itself is removed via `cmd /c rmdir`. The external source folder it pointed at is **never touched**. Follow `.claude/skills/_shared/dayz-conventions.md`. ## How to run ```cmd python "\clean.py" [--mod ] [--include-server] [--yes] [--dry-run] ``` | Argument | Required? | Notes | |---|---|---| | `--mod ` | no | Target a specific mod by name. Default: all scaffolded mods under `workspace/`. | | `--include-server` | no | Also remove `.server/` at the project root (all instances: missions, configs, profiles, client logs). Refuses if legacy `workspace/_server/` still exists. | | `--yes` | no | Skip the interactive confirmation prompt. Required when stdin isn't a TTY. | | `--dry-run` | no | Print what would be removed; touch nothing. Always exit 0. | ## What it removes (per scaffolded mod) For each `workspace//` containing `config.cpp` + `$PBOPREFIX$`: | Artifact | Removed when | |---|---| | `P:\\` junction | It exists AND points at `workspace//`. (If the link points elsewhere or isn't a link, it's left alone - could be the user's own setup.) | | `P:\Mods\@\` deployed dir | It exists AND contains the ownership marker `.agentic-z-scaffold` with content matching ``. The marker is dropped by `/dayz-build-pbo` on every successful build, so any deployed dir we produced will have it. Without the marker, the dir is skipped with a `[WARN]` and a manual rmdir hint - protects against name collisions with hand-placed or subscribed mods. | | `workspace//` (native scaffold) | Always. Folder + contents removed recursively via `shutil.rmtree`. | | `workspace//` (imported link) | The link itself is removed via `cmd /c rmdir` (the same approach used for `P:\\`). The link's target - your external mod source - is **never touched**. Output kind shows as `workspace-link` to make this visible. | ### Note on existing deployed dirs If you have deployed dirs from before the marker was introduced, they won't have `.agentic-z-scaffold` and `dayz-clean-workspace` will skip them. Either rebuild via `/dayz-build-pbo ` (which writes the marker) or remove manually with `cmd /c rmdir /s /q P:\Mods\@` after confirming it's actually yours. With `--include-server`, also removes `.server/` at the project root (all instances under it: missions, configs, profiles, client logs). Use this for a full reset; otherwise the server staging stays so you don't have to re-copy missions next time. If `workspace/_server/` (the legacy layout) still exists, this skill refuses; delete the folder manually first (the previous `dayz-migrate-server` skill that copied content to `.server//` was removed in 1.4.0). ## What it WILL NOT touch - Mods you installed via Steam Workshop or DayZ Launcher (they live under `\!Workshop\@\` and only `@` matches are removed). - `P:\\` junctions or folders that don't correspond to a `workspace//` entry. - `P:\Mods\` itself (the junction stays - only the `@\` subfolders within it that match managed mods are removed). - **External source folders for imported mods**. If `workspace//` is a `/dayz-import-mod` link pointing at, say, `C:\Users\you\repos\MyMod`, only the link is removed - your source folder stays exactly as it was. The clean output kind shows as `workspace-link` to make this visible. - Anything outside `workspace/`, `P:\\` for matched names, or `P:\Mods\@\` for matched names. ## Refuses to run if - `/dayz-preflight` returns non-zero. - `--mod ` is given but `workspace//` isn't a scaffolded mod (no `config.cpp` / `$PBOPREFIX$`). - Stdin isn't a TTY and `--yes` wasn't passed (refuses to silently destroy without an explicit confirmation). ## Output Native scaffold: ``` Plan: 3 item(s) to remove (junction) P:\NativeMod (deployed) P:\Mods\@NativeMod (workspace) workspace\NativeMod Proceed? [y/N]: y [OK] removed (junction): P:\NativeMod [OK] removed (deployed): P:\Mods\@NativeMod [OK] removed (workspace): workspace\NativeMod [OK] Cleaned 3 item(s). ``` Imported mod (`workspace-link` kind = link removed, source untouched): ``` Plan: 2 item(s) to remove (junction) P:\MyMod (workspace-link) workspace\MyMod Proceed? [y/N]: y [OK] removed (junction): P:\MyMod [OK] removed (workspace-link): workspace\MyMod [OK] Cleaned 2 item(s). ``` `--dry-run` form prints the plan with `would remove` prefix and exits without changes. ## Do not - Don't add the ability to remove arbitrary `P:\Mods\@\` entries that don't correspond to a `workspace//` scaffold. The match-on-scaffold rule is what makes this skill safe to run against a machine with subscribed mods. - Don't follow junctions during removal. Use `cmd /c rmdir` (which removes the junction without descending into the target). Plain `rm -rf` on a junction is unreliable on Windows / Git Bash. - Don't gate this skill behind any "are you sure" beyond the `--yes` / TTY confirmation. Two prompts are noise.