メニュー
Quarantine Windows-locked DLL/EXE/PYD artifacts with clud trash instead of retrying deletes or killing processes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
File a deeply-researched GitHub issue via investigate → investigate → post, returning a summary plus the issue URL. Files without asking for confirmation.
Spin up a fast Linux build container for a Rust + soldr + zccache, Python (uv), or C++ (CMake + ccache) project using the bundled `docker-build` tool family. Uses anonymous Docker volumes for build state and a read-only bind for source — the one rule that turns Docker-Desktop's 20-minute cold-build into a sub-30-second warm cycle.
Diagnose and recover a wedged Docker Desktop (engine pipe/socket absent while the UI stays alive, WSL/Docker startup failures) and answer Docker VM disk-growth / memory-pressure questions. Read-only `doctor` first; every restart/reset is confirmation-gated and preserves images/volumes; storage disks are resolved from Docker Desktop's real config (never assumed) and never compacted or deleted automatically.
Coordinate dependent cross-repo changes under a repo-local .extern-repos/ checkout convention.
Show a git diff in a native OS webview window (Beyond Compare-style dual-pane with file picker on the left) via the bundled git/clud-git-diff.py tool. Invoke when the user asks to visually review changes between revisions.
Worktree, branch, process-audit, and quarantine playbook extracted from /clud-pr so /clud-fix-quick and other skills can reuse it. Use this when the user asks for worktree cleanup, stale-branch teardown, or a process audit on a leftover dir.
| name | clud-windows-trash |
| description | Quarantine Windows-locked DLL/EXE/PYD artifacts with clud trash instead of retrying deletes or killing processes. |
| triggers | ["When deleting *.dll, *.pyd, or *.exe on Windows fails with os error 32 or being used by another process","When a build fails because an output DLL, PYD, or EXE is locked","When a directory containing Windows build artifacts cannot be removed"] |
Use clud trash when Windows refuses to delete freshly built native artifacts.
If trashing a locked artifact unblocks a bug fix or feature implementation, continue with RED -> GREEN: prove the focused test/repro fails before the code change, implement the scoped fix, then rerun that signal until it passes.
*.dll, *.pyd, or *.exe fails with os error 32, being used by another process, Access is denied, or similar loader/Defender lock symptoms.del, Remove-Item, or rm in a loop.taskkill for guessed parent processes.clud trash <path> for the locked file or containing directory, then continue the build or cleanup.clud trash reports a source/trash volume mismatch, pass --cross-volume only when the copy cost is acceptable: clud trash --cross-volume <path>.clud trash <path>.~/.clud/trash/ until Windows releases the lock.--cross-volume. Source removal after the copy is best-effort.clud gc list --kind trash.After a successful trash, keep going. Do not wait for the daemon to reap the quarantined path unless the user explicitly asks to verify cleanup.