Stats
Actions
Tags
From dev-on-leash
Use to escape a session-leash block. Creates a sibling git worktree for this Claude Code session and flips its lockfile to in-worktree so write tools unblock. Invoke as your next action when SessionStart said this session is concurrent.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-on-leash:leash-session-newThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The `SessionStart` hook reported `SESSION LEASH: concurrent Claude Code
The SessionStart hook reported SESSION LEASH: concurrent Claude Code session detected, and PreToolUse is now denying Edit, Write, and
MultiEdit. You MUST invoke this skill before any other tool call.
Do NOT use this when only one Claude Code session is open in this repo — it will refuse with a clear message.
Run the backing script:
python -m scripts.harness.session_new
The script:
.harness/sessions/<pid>.json../<repo>--session-<id>/ on a new
session/<id> branch from the trunk (main/master, else HEAD)in-worktreeThe script prints the worktree path. From that point on, use
absolute paths under that directory for every Edit, Write,
MultiEdit, and file Read. Your session cwd has not moved; this
is intentional.
The skill is idempotent. Running it twice returns the same worktree.
main/master) — not the primary checkout's HEAD — so it stays
independently mergeable. It only falls back to HEAD when the repo has
neither main nor master.PreToolUse gate will keep denying writes./leash-session-end to remove the worktree
and clean up.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub diogeneshfg/dev-on-leash --plugin dev-on-leash