What problem does it solve? When multiple coding agents (Claude, Codex, or others) work on the same machine, two agents can edit the same git worktree or directory simultaneously and corrupt each other's work. This Skill provides a vendor-neutral, file-based lock so only one agent holds write occupancy of a directory at any moment. ## Core Features & Use Cases - Atomic lock claiming: Creates a lock via exclusive file creation keyed by the resolved directory realpath, with pid-based liveness detection and automatic takeover of stale locks whose holder process has died. - Full lock lifecycle: Commands to claim, check, release, and release-all locks, plus an exclude/include list for directories that should never be locked (such as /tmp or agent config homes). - Required work descriptions: Every lock records a human-readable description of the change being made, so a blocked agent can tell the operator which session holds a directory and what it was doing. - Use Case: A Claude session and a Codex session both try to edit the same repository. The first claims the lock with a description; the second is refused, sees who holds it, and spins up a separate git worktree instead of colliding. ## Quick Start Ask the agent to claim dibs on the current project directory with a short description of the change before making any edits.
