clud-windows-trash

스타9

포크0

업데이트2026년 6월 3일 03:19

Quarantine Windows-locked DLL/EXE/PYD artifacts with clud trash instead of retrying deletes or killing processes.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

zackees

zackees/clud

GitHub 저장소 열기 Creator 저장소 보기

다운로드

/clud-windows-trash

Use clud trash when Windows refuses to delete freshly built native artifacts.

Code Change Rule

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.

Triggers

A delete of *.dll, *.pyd, or *.exe fails with os error 32, being used by another process, Access is denied, or similar loader/Defender lock symptoms.
A build script cannot overwrite an output file because the previous artifact is still locked.
A directory removal fails and the tree contains Windows native build outputs.

Rules

Do not retry del, Remove-Item, or rm in a loop.
Do not run taskkill for guessed parent processes.
Run clud trash <path> for the locked file or containing directory, then continue the build or cleanup.
If clud trash reports a source/trash volume mismatch, pass --cross-volume only when the copy cost is acceptable: clud trash --cross-volume <path>.

Workflow

Identify the smallest locked path that unblocks the build. Prefer the exact file; use the containing build-output directory when many siblings are blocked.
Run clud trash <path>.
If the command succeeds, proceed immediately. The clud daemon will retry deletion from ~/.clud/trash/ until Windows releases the lock.
If cross-volume copy is required and acceptable, rerun with --cross-volume. Source removal after the copy is best-effort.
To inspect pending cleanup, run clud gc list --kind trash.

Exit Guidance

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.

이 저장소의 다른 Skills

같은 저장소

clud-issue

zackees/clud

File a deeply-researched GitHub issue via investigate → investigate → post, returning a summary plus the issue URL. Files without asking for confirmation.

2026-08-039

clud-docker-linux-build

zackees/clud

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.

2026-08-019

clud-docker-recover

zackees/clud

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.

2026-07-319

clud-extern-repos

zackees/clud

Coordinate dependent cross-repo changes under a repo-local .extern-repos/ checkout convention.

2026-06-239

clud-git-diff

zackees/clud

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.

2026-06-209

clud-git

zackees/clud

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.

2026-06-209

/clud-windows-trash

Use clud trash when Windows refuses to delete freshly built native artifacts.

Code Change Rule

Triggers

A delete of *.dll, *.pyd, or *.exe fails with os error 32, being used by another process, Access is denied, or similar loader/Defender lock symptoms.

A build script cannot overwrite an output file because the previous artifact is still locked.

A directory removal fails and the tree contains Windows native build outputs.

Rules

Do not retry del, Remove-Item, or rm in a loop.

Do not run taskkill for guessed parent processes.

Run clud trash <path> for the locked file or containing directory, then continue the build or cleanup.

If clud trash reports a source/trash volume mismatch, pass --cross-volume only when the copy cost is acceptable: clud trash --cross-volume <path>.

Workflow

Identify the smallest locked path that unblocks the build. Prefer the exact file; use the containing build-output directory when many siblings are blocked.

Run clud trash <path>.

If the command succeeds, proceed immediately. The clud daemon will retry deletion from ~/.clud/trash/ until Windows releases the lock.

If cross-volume copy is required and acceptable, rerun with --cross-volume. Source removal after the copy is best-effort.

To inspect pending cleanup, run clud gc list --kind trash.

Exit Guidance

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.

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"]

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"]