Create an isolated Git worktree on an auto-named branch after validating a clean repository state.
npx skills add https://github.com/Levezze/devkit --skill worktree-levezze
Please help me install this Agent Skill. Skill: worktree Source: https://github.com/Levezze/devkit/tree/main/skills/worktree Command: npx skills add https://github.com/Levezze/devkit --skill worktree-levezze
It solves the friction of starting work on a new feature or fix by isolating your changes in a fresh git worktree with a disciplined, context-derived branch name.
feat/, fix/, chore/, or docs/ branch name from /worktree arguments and conversation artifacts (issue numbers, handoffs, PRDs/grill sessions), with normalization and validation.EnterWorktree, verifies cleanliness, and instructs explicit exit behavior later.Ask your AI to run the worktree skill to start an isolated session with an auto-named branch for your current task: use /worktree.
High-intent search queries and answers about installing and using this skill.
To create an isolated git worktree safely, the skill runs a pre-flight validation on your repository to detect a dirty state, prompts you to commit or stash, and then spins up a clean worktree on an auto-named feature branch.
Context-aware branch naming builds a readable branch name by extracting issue numbers, PRDs, and handoff context from your conversation, then normalizing them into standardized prefixes like feat/, fix/, chore/, or docs/.
Yes, but the dirty-tree safety gate intercepts the creation process to prevent unsafe use, forcing an explicit choice to commit, stash, proceed with a warning, or cancel before initializing the worktree.
The best way to isolate mid-session work is invoking /worktree during a task transition, which triggers deterministic branch-name derivation, EnterWorktree execution, and a post-entry cleanliness confirmation.
A key limitation is that worktree transitions require a clean repository state to proceed safely; if the git status pre-flight validation fails, the workflow pauses until you resolve the dirty tree conflict.
No, you do not need to manually name your branch; the skill applies deterministic branch-name derivation using your /worktree arguments and conversation artifacts to normalize a valid branch name automatically.
CHNISamCreate isolated Git worktree environments and verify directory ignore status.
DMT123Verify tests, then merge, create a pull request, or discard a development branch.
e-stpierreCreate and checkout git branches with standardized kebab-case naming.
homeassistant-aiCreate a git worktree under worktree/<branch> and update submodules.