Provisions a dedicated git worktree and branch for an active task.
npx skills add https://github.com/Mozurok/fhorja.dev --skill task-workspace-mozurok
Please help me install this Agent Skill. Skill: task-workspace Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/task-workspace Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill task-workspace-mozurok
task/<task-dir>) off the base branch, kept outside the main working tree. - Status and attach actions: Reports an existing worktree read-only, or retrofits a worktree onto a task already in progress. - Safe by default: Git-gated and opt-in, with branch-collision detection, no forced checkouts, no teardown, and a recorded ## Workspace section in SOURCE_OF_TRUTH.md. - Use Case: You are running three feature tasks against one repository in parallel. Run this Skill for each task so every task gets its own worktree and branch, and task-close can later tear each one down cleanly. ## Quick Start Ask the agent to provision an isolated git worktree and branch for the current active task and record it in SOURCE_OF_TRUTH.md.High-intent search queries and answers about installing and using this skill.
Create a dedicated git worktree and branch per task so each task has its own working tree. This Skill derives the branch as task/<task-dir> and places the worktree outside the main tree, then records both in SOURCE_OF_TRUTH.md.
Use the attach action, which runs the same provisioning against the current base branch without touching other task-memory files. It only writes the Workspace section into SOURCE_OF_TRUTH.md so downstream commands can find the worktree.
Git allows a branch to be checked out in only one worktree at a time. The Skill checks git worktree list before adding, stops on a collision instead of forcing, and attaches to an existing branch only when it is not checked out anywhere.
No. The Skill runs a git gate first and returns a NO_OP_TRACE on non-git projects, leaving the task on the single working tree unchanged. Multi-repo tasks are also unsupported and receive an explicit refusal.
Do not use it for ephemeral slice-level worktrees, which implement-fleet manages and tears down itself, or for removing worktrees, which task-close owns. It is also a no-op when isolation was never requested.
ChazzCoinProvision isolated prototype branches and task structures with lifecycle commands.
kelsi-andrewssAutomates cleanup of Git worktrees, branches, and epics with dry-run option.
vr000mRun multiple Claude agents in parallel across isolated git worktrees.
Brite-NitesCreate isolated git worktrees with branches named after Linear issue IDs.