What problem does it solve? Removing a job's workspace by hand risks destroying uncommitted work or deleting an unmerged branch, since a worktree is the only record of its uncommitted changes. This Skill enforces safety gates before any teardown so nothing is lost silently. ## Core Features & Use Cases - Safety Gates: Refuses to proceed when the worktree has uncommitted changes or the job branch is not fully merged into the remote's actual integration branch (resolved via git ls-remote --symref origin HEAD). - Scoped Runtime Teardown: Stops the workspace's docker-compose stack with a project-scoped down --volumes, or reports still-listening dev-server processes without killing them. - Clean Removal: Removes the worktree without --force and deletes the branch with git branch -d, then reports what was torn down, the surviving merge commit, and any leftovers. - Use Case: After finishing a feature job in an isolated worktree, run /close <job> to verify the work is committed and merged, then tear down the stack, worktree, and branch in one safe operation. ## Quick Start Ask the assistant to close the workspace for job slug "auth-refactor" by running /close auth-refactor.
